基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/vstorm-co/agenticos --skill technical-documentation-lookup命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | Technical documentation lookup |
| description | Answer from the right revision of a drawing or manual, and say which one. |
| category | documentation |
The commonest failure is not a wrong answer. It is a right answer from a superseded revision.
The document, its revision, and its date. Then the answer, quoted. A specification without its revision is unusable on the shop floor.
The part being worked on may have been built to an earlier revision. Ask which serial or batch, and answer against the revision that applies to it — not against the latest.
Quote tolerances exactly as written, with the units and the datum. Never convert silently; if a conversion is needed, give both and say which is the controlled one.
Name both, with revisions, and stop. The drawing usually governs over the manual, but saying so is engineering's call.
Answer from an uncontrolled copy, round a tolerance, or infer a dimension from a drawing that is marked not to scale.
Write or extend the backend Python test suite — a unit test for a service, an integration test against a real Postgres, an API test through the FastAPI app, or the test a bug fix needs. Also for "coverage is failing", "make test is red", and deciding which of the four layers a test belongs in. Uses anyio (not pytest-asyncio) and a 100% coverage gate on the platform layer.
Build or change a page, view or data-driven feature in the Next.js frontend — a route under the dashboard, wiring UI to a backend endpoint, a Zustand store, a permission that must hide a control, or localized copy. Use for any work in frontend/src, including "the page renders but shows an empty state" and "this button should not be visible to a Viewer".
Write or fix the documentation site — add a page, update one after a behaviour change, fix a dead link or a failing docs build, add a diagram or an icon, or wire a new page into the nav. Use whenever docs/ or mkdocs.yml is touched, and whenever a code change alters behaviour a page describes. make docs-build runs --strict, so a dead link fails CI.