.claude/skills/<skill-name>1 structural issue
- error: The fixed release did not provide readable SKILL.md content.
SKILL.md
Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.
Drive development from authoritative source documentation and specifications
These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.
These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.
.claude/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
.agents/skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
skills/<skill-name>SKILL.mdRuntime, accounts, dependencies, permissions, network behavior and task quality remain untested.
This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.
clawhub install @paudyyin/source-driven-developmentclawhub inspect @paudyyin/source-driven-development --version 1.0.0This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.
content unavailableThis is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.
The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.
sha256:8dd5b151a8dddce9b0a413ad57538aa44d3b6a20f1e46253d87e7cd43152b944skill-card.mdSKILL.mdInitial release of source-driven-development. - Defines a workflow for making framework-specific code decisions based on official documentation and specifications. - Outlines when source-driven development is appropriate and when it is not. - Details a step-by-step process: detect stack and version, retrieve authoritative documentation, implement per documentation, and cite sources. - Provides strict rules for referencing (deep links, no blogs or AI summaries) and handling unverifiable content. - Includes checklists, red flags, and inter-skill relationships for quality assurance. - Emphasizes transparency, accuracy, and version sensitivity in framework-driven code.