6b3b2abe4f
73 stackexchange-grounded, 516 model-knowledge (ESCO-seeded gemma3), 0 review_needed (calibration caveat documented). Adapters rebuilt with the full competence sets; final REPORT numbers; all verify checks pass. Known gap: engineering-manager lacks an ESCO package counterpart. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PDKeXvpT6tENSvyQGLV1Uq
1.3 KiB
esco_uri, esco_label, relation, onet_soc, source, confidence, qa_count, generator, generated
| esco_uri | esco_label | relation | onet_soc | source | confidence | qa_count | generator | generated |
|---|---|---|---|---|---|---|---|---|
| http://data.europa.eu/esco/skill/85c11255-469f-41bd-a6d1-382bc4a87783 | interpret technical texts | essential | 15-1242.00 | model-knowledge | high | 0 | gemma3:27b (prompt-designed and spot-checked by Claude) | 2026-07-10 |
interpret technical texts — Database Administrator
As a Database Administrator (DBA), 'interpreting technical texts' isn’t about literary analysis; it's essential for daily problem solving and maintenance. You'll constantly encounter documentation – vendor manuals for your specific database system (Oracle, SQL Server, PostgreSQL, etc.), release notes detailing new features or security patches, error messages requiring you to look up root causes in knowledge bases, and configuration guides for tools like replication software or backup solutions. A typical task might involve deciphering a complex error message from the database logs, then cross-referencing it with the vendor's documentation to identify the failing component and recommended fix. It’s about quickly extracting actionable information from often dense, jargon-filled writing.
Weitere Anreicherung
Stage-2 source for future practitioner grounding: arXiv cs.SE (software-engineering preprints).