project-guide
Simulates plan mode with a teaching-first approach. Use when onboarding to a new codebase, exploring architecture, or seeking guided understanding of any project area. Produces high-level overviews with diagrams, drills into details on request, and offers follow-up exploration questions.
Install with Tessl CLI
npx tessl i github:0xrabbidfly/eric-cartman --skill project-guide85
Quality
83%
Does it follow best practices?
Impact
84%
1.33xAverage score across 3 eval scenarios
Discovery
82%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 description that clearly communicates both purpose and trigger conditions. It uses appropriate third-person voice and includes natural trigger terms for codebase exploration scenarios. The main weakness is that some capabilities are described abstractly ('drills into details') rather than with concrete actions, and there's potential overlap with other code explanation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (teaching/onboarding) and some actions ('produces high-level overviews with diagrams', 'drills into details', 'offers follow-up exploration questions'), but actions are somewhat abstract rather than concrete technical operations. | 2 / 3 |
Completeness | Clearly answers both what ('Simulates plan mode with teaching-first approach', 'produces overviews with diagrams', 'drills into details', 'offers follow-up questions') and when ('Use when onboarding to a new codebase, exploring architecture, or seeking guided understanding'). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'onboarding', 'new codebase', 'exploring architecture', 'guided understanding', 'project area'. These are phrases developers naturally use when seeking orientation help. | 3 / 3 |
Distinctiveness Conflict Risk | The teaching/onboarding niche is fairly specific, but 'exploring architecture' and 'guided understanding' could overlap with general code explanation or documentation skills. The 'plan mode' reference helps distinguish it somewhat. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%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-structured skill with excellent actionability and workflow clarity. The four-phase exploration model with concrete output templates gives Claude clear guidance on how to conduct guided tours. The main weakness is some verbosity in the teaching philosophy and adaptive techniques sections that could be tightened without losing value.
Suggestions
Condense the 'Teaching Philosophy' section—Claude understands pedagogical principles; focus on the specific behaviors expected rather than explaining why they matter
Trim the 'Adaptive Teaching Techniques' section to a compact table or bullet list rather than detailed prose for each audience type
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is well-organized but includes some unnecessary verbosity, such as the philosophy section and extensive template examples that could be condensed. The anti-patterns table and some explanatory prose add tokens without proportional value. | 2 / 3 |
Actionability | Provides concrete output templates, specific Mermaid and ASCII diagram examples, clear phase-by-phase workflows, and copy-paste ready markdown formats. The example session flow demonstrates exactly how interactions should proceed. | 3 / 3 |
Workflow Clarity | The four-phase workflow (First Impressions → Architecture → Focused Exploration → Follow-Up Questions) is clearly sequenced with explicit output formats for each phase. The example session flow demonstrates the complete interaction pattern. | 3 / 3 |
Progressive Disclosure | Excellent structure with quick start at top, detailed phases in middle, and supporting files referenced at the end. References to diagram-patterns.md and interaction-template.md are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.