ghost-repo-context
Scans directory structure, detects projects, maps dependencies, and documents code organization into a repo.md file. Use when the user needs a codebase overview, project structure map, or repository context before security analysis.
Install with Tessl CLI
npx tessl i github:ghostsecurity/skills --skill ghost-repo-context99
Does it follow best practices?
Evaluation — 100%
↑ 3.57xAgent success when using this skill
Validation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes natural trigger terms users would actually say, explicitly states both what the skill does and when to use it, and carves out a distinct niche that minimizes conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Scans directory structure', 'detects projects', 'maps dependencies', and 'documents code organization into a repo.md file'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (scans, detects, maps, documents) AND when ('Use when the user needs a codebase overview, project structure map, or repository context before security analysis'). Explicit 'Use when...' clause is present. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'codebase overview', 'project structure map', 'repository context', 'directory structure', 'dependencies'. These cover common variations of how users might request this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on repository scanning and documentation into repo.md specifically. The combination of directory scanning, dependency mapping, and security analysis context creates a distinct trigger profile unlikely to conflict with general code or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that demonstrates excellent token efficiency while providing fully actionable guidance. The workflow is clearly sequenced with appropriate validation checkpoints and error recovery paths. The progressive disclosure pattern is exemplary, using the main skill file as an orchestrator that references specialized sub-files at the right moments.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, assuming Claude's competence. No unnecessary explanations of concepts Claude already knows, and every section serves a clear purpose. | 3 / 3 |
Actionability | Provides executable bash commands, specific file paths to reference, and concrete steps. The workflow is copy-paste ready with clear variable handling and fallback computations. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with explicit validation in step 4 (read back and verify), error handling (retry once), and conditional logic (cache check, no-projects-detected path). Includes feedback loop for malformed output. | 3 / 3 |
Progressive Disclosure | Excellent structure with SKILL.md as overview pointing to one-level-deep references (detector.md, summarizer.md, template-repo.md). Clear navigation signals for when to read each referenced file. | 3 / 3 |
Total | 12 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.