Writing new code and delivering it in small steps: naming, error handling, lint and type gates, walking skeletons, always-green commits, time-boxed spikes, and docs-as-code inside the repo. Use when asking "implement this""split this feature into small shippable steps keeping main green",, "write the function", "how should I name this", "how should this handle errors", "build it step by step", "walking skeleton", "keep main green", "quick prototype to test this", "spike this for two days", "add docstrings", "generate the API reference". Not for planning the task list or estimates, cleaning up existing working code as a goal in itself, choosing the test portfolio, or branch policy; those sit outside this skill.
cp -r cryptoskill/skills/exchanges/anoscranel-ac-code-construction .claude/skills/clawhub install anoscranel-ac-code-constructionCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
unknown
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed