Install
$ agentstack add skill-guohao1020-docs-cockpit-use-docs-cockpit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
use-docs-cockpit
> [Session context · docs-cockpit router] This block is injected at session start in any project with a docs-cockpit.yaml. Its only job: route you to the right skill before you act on any docs-cockpit-related intent.
This project manages its documentation association system (module ↔ subtask ↔ spec/plan/RFC anchors) with docs-cockpit. North-star: cognition lives in skills, Python only renders — and anchor precision comes first: a wrong anchor is worse than a missing anchor.
This file is a router only. Each routed skill carries its own complete workflow — read it before acting; do not improvise doc-association work from here.
Routing
| You want to | Use | Trigger examples | |---|---|---| | Build or extend the association system — set up the cockpit itself (config + scan dirs + debug build issues), plan the whole project's spec/plan, wire modules to docs, fill anchor gaps (0→1 / whole-project) | docs-cockpit-build skill | 「把项目做成看板」「把文档体系建起来」「关联模块和文档」「规划 spec」 | | Refresh an EXISTING association that drifted — anchors stale after refactor, spec evolved and links need re-sync | docs-cockpit-rebuild skill | 「关联乱了重新梳理」「anchor 失效了」 | | Just regenerate the dashboard HTML, no association work | CLI docs-cockpit render | 「重新生成 dashboard」 | | Read status / progress / blockers, no file changes | docs-cockpit-rebuild Phase 1 (pure status queries end there) | 「项目进度怎么样」「哪些卡了」 | | Run a project health checkup / 健康检查 (existing cockpit — the report feeds the dashboard health panel) | docs-cockpit-rebuild skill | 「体检一下」 "run a health check" | | Upgrade docs-cockpit itself | CLI docs-cockpit upgrade (see references/operations.md · upgrade) | 「升级 docs-cockpit」 "update docs-cockpit" |
Discriminator between the two skills: build = the association does not exist yet (or whole-project planning); rebuild = it already exists and needs diagnosis / refresh (or just reading).
When NOT to apply
If the project has no docs-cockpit.yaml at the repo root, this router does not apply — the project does not use docs-cockpit. (The SessionStart hook injects this file conditionally, but a marketplace install can also trigger it directly; check for the config first.)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Guohao1020
- Source: Guohao1020/docs-cockpit
- License: MIT
- Homepage: https://github.com/Guohao1020/docs-cockpit#quickstart--60-seconds
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.