git-submodule
Manage Git submodules for including external repositories within a main repository. Use when working with external libraries, shared modules, or managing dependencies as separate Git repositories.
84
77%
Does it follow best practices?
Impact
96%
1.18xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/git-submodule/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description with excellent completeness and distinctiveness. It clearly explains both what the skill does and when to use it, with good trigger terms. The main weakness is the lack of specific concrete actions beyond the generic 'manage' verb.
Suggestions
Add specific concrete actions like 'add, update, remove, and sync Git submodules' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Git submodules) and general action (manage), but lacks specific concrete actions like 'add submodules', 'update submodules', 'remove submodules', or 'sync submodule URLs'. | 2 / 3 |
Completeness | Clearly answers both what ('Manage Git submodules for including external repositories within a main repository') and when ('Use when working with external libraries, shared modules, or managing dependencies as separate Git repositories') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes good natural keywords users would say: 'Git submodules', 'external repositories', 'external libraries', 'shared modules', 'dependencies', 'separate Git repositories'. These cover common variations of how users describe submodule work. | 3 / 3 |
Distinctiveness Conflict Risk | Git submodules is a clear niche with distinct triggers. The specific mention of 'submodules', 'external repositories within a main repository', and 'dependencies as separate Git repositories' distinguishes it from general Git skills or dependency management tools. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable Git submodule reference with excellent executable examples covering all common use cases. However, it's verbose for a skill file, explaining concepts Claude already knows, and lacks validation checkpoints for potentially destructive operations like submodule removal and batch commands. The monolithic structure could be improved by splitting into a concise overview with references to detailed guides.
Suggestions
Remove explanatory prose like 'Git submodule is a feature for...' and 'Key concepts' section - Claude knows these fundamentals
Add explicit validation steps after destructive operations (e.g., 'Verify removal: git submodule status' after removing a submodule)
Split into SKILL.md (quick reference with common commands) and separate files for TROUBLESHOOTING.md, ADVANCED.md, and CI_CD.md
Add feedback loops for batch operations: 'git submodule foreach' should include verification that all submodules succeeded
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations like 'Git submodule is a feature for including other Git repositories within a main Git repository' which Claude already knows. The content could be tightened by removing explanatory prose and keeping just the commands and examples. | 2 / 3 |
Actionability | Excellent executable code throughout with copy-paste ready bash commands, complete examples for all common operations, and specific CI/CD configurations. Every section provides concrete, runnable commands rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced, but validation checkpoints are largely missing. For destructive operations like removing submodules or batch operations with 'foreach', there are no explicit verification steps or feedback loops to catch errors before proceeding. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it's a monolithic document (~350 lines) that could benefit from splitting advanced workflows, troubleshooting, and configuration into separate reference files. External references are only provided at the end rather than integrated throughout. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.