What it may solve
怀疑驱动开发:每个非平凡决策在落地前接受新鲜上下文的对抗性审查(CLAIM→EXTRACT→DOUBT→RECONCILE→STOP)。受 addyosmani/agent-skills(88k★ MIT)启发。
Imported third-party catalog description; not a Registry verification conclusion.怀疑驱动开发:每个非平凡决策在落地前接受新鲜上下文的对抗性审查(CLAIM→EXTRACT→DOUBT→RECONCILE→STOP)。受 addyosmani/agent-skills(88k★ MIT)启发。
Author: satan9394 · Skills · Catalog snapshot: 2026-09-19Canonical semantic path
怀疑驱动开发:每个非平凡决策在落地前接受新鲜上下文的对抗性审查(CLAIM→EXTRACT→DOUBT→RECONCILE→STOP)。受 addyosmani/agent-skills(88k★ MIT)启发。
Imported third-party catalog description; not a Registry verification conclusion.satan9394/dsh-doubt-driven-dev
— stars · 184 downloads
Signals were provided by the source catalog and do not imply quality or safety. 2026-09-19Active analysis coverage 5/5. Historical chains are retained but do not count toward current coverage.
Conclusion: The source structure check completed without finding a structural issue.
Conclusion: The GitHub repository could not be confirmed as reachable.
Conclusion: Resolved npm release 0.1.0, published 2026-08-19, license MIT.
Conclusion: Compatibility verification passed. Installation, profile loading, and sustained startup all completed. Test environment: DSH 0.1.6-alpha.2, web profile.
Conclusion: This bounded audit reported 0 known vulnerabilities. It covers only the locked versions and audit source; zero reports is not proof of safety.
The plugin’s advertised feature has not been automatically verified. Passing installation and startup does not prove that feature works.
Conclusion: The bounded static scan found none of its predefined risk signals. This is not proof of safety.
Conclusion: Package name, version, entrypoints, and checksum passed validation. Artifact: dsh-doubt-driven-dev@0.1.0; SHA-256: 198a90244b363795b833f7f09be8413240edbfcdf96c4d4bb67b24314dd80683.
Automated evidence is scoped to the named artifact, DSH target and profile. It is not a blanket safety or feature-completeness claim.
Describe your task in a DSH conversation and mention dsh-doubt-driven-dev. After installing or updating the manager from npm latest, it can find this candidate through Registry, then inspect its actual source and version locally.
dsh-doubt-driven-devAnalyzed 0.1.0github:satan9394/dsh-doubt-driven-devExact version not resolved