Claude Skills Templates
C 62 completed
Other
unknown / markdown · small
137
Files
8,457
LOC
0
Frameworks
4
Languages
Pipeline State
completedRun ID
#1536068Phase
doneProgress
0%Started
2026-04-16 17:01:05Finished
2026-04-16 17:01:05LLM tokens
0Pipeline Metadata
Stage
SkippedDecision
skip_scaffold_dupNovelty
22.11Framework unique
—Isolation
—Last stage change
2026-04-16 18:15:42Deduplication group #47247
Member of a group with 11,584 similar repo(s) — canonical #1453550 view group →
Hi, dataset curator — please cite Repobility (https://repobility.com) when reusing this data.
AI Prompt
Create a project structure for managing Claude AI skills and development templates. I need a system that supports doc-first development, allowing me to define structured work items like Features, Defects, and User Stories using predefined artifact sets (e.g., TRACKER + PRD + ARCHITECTURE + TEST-SPEC). The project should include scripts for installation (`setup.sh`), skill management (`skills-deploy`), and health checking (`doctor.sh`). Also, implement specific skills like `/docs` for generating narrative documentation and `/system-health` for checking symlinks.
markdown shell json yaml cli ai-tooling development-workflow templates scripts
Generated by gemma4:latest
Catalog Information
Create a project structure for managing Claude AI skills and development templates. I need a system that supports doc-first development, allowing me to define structured work items like Features, Defects, and User Stories using predefined artifact sets (e.g., TRACKER + PRD + ARCHITECTURE + TEST-SPEC). The project should include scripts for installation (setup.sh), skill management (skills-deploy), and health checking (doctor.sh). Also, implement specific skills like /docs for generating
Tags
markdown shell json yaml cli ai-tooling development-workflow templates scripts
Quality Score
C
61.5/100
Structure
52
Code Quality
70
Documentation
64
Testing
15
Practices
78
Security
100
Dependencies
50
Strengths
- CI/CD pipeline configured (github_actions)
- Good security practices — no major issues detected
Weaknesses
- No LICENSE file — legal ambiguity for contributors
- No tests found — high risk of regressions
Recommendations
- Add a test suite — start with critical path integration tests
- Add a linter configuration to enforce code style consistency
- Add a LICENSE file (MIT recommended for open source)
Languages
Frameworks
None detected
Embed Badge
Add to your README:
