CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

79

1.33x
Quality

73%

Does it follow best practices?

Impact

84%

1.33x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/project-guide/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, actionable teaching skill with clear phased workflows and concrete templates, but it runs long for a context-window-sensitive skill and, critically, references two bundle files (diagram-patterns.md, interaction-template.md) that do not exist, breaking progressive disclosure.

Suggestions

Create the referenced diagram-patterns.md and interaction-template.md (or remove the broken links) so the signaled navigation actually resolves.

Trim padding Claude doesn't need: the ASCII fallback diagram, the full example session flow, and the closing inspirational quote.

Move the full inline output-format templates and Mermaid example into the referenced files, leaving SKILL.md as a lean overview that links out.

DimensionReasoningScore

Conciseness

The body is purposefully structured but ~340 lines with padding that Claude doesn't need (ASCII art diagrams, a full example Mermaid graph, a sample session flow, an inspirational closing quote, and some generic mental-model framing). Matches 'mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 2 because the structure is intentional, not heavily padded; not a 4 because several sections (ASCII fallback, example session flow, closing quote) could be trimmed.

3 / 5

Actionability

Provides concrete, reusable output templates (Project Overview, Deep Dive, Where to Next scaffolds), real Mermaid/ASCII diagram examples, and question-pattern tables, matching 'mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because templates rely on illustrative placeholders like [One sentence description] rather than being copy-paste-ready for a specific task; not a 3 because the guidance is well beyond pseudocode.

4 / 5

Workflow Clarity

Four clearly sequenced phases (First Impressions -> Architecture -> Focused Exploration -> Follow-Up) each with numbered sub-steps and a worked example flow, matching 'clear sequence with most checkpoints present'. Not a 5 because checkpoints (assess familiarity, set context) are implicit rather than explicit validation steps; not a 3 because the sequence is genuinely clear and well-defined, not merely 'steps listed'.

4 / 5

Progressive Disclosure

Good section structure and one-level-deep references to diagram-patterns.md and interaction-template.md, but neither referenced file exists in references/, scripts/, or assets/, so the signaled navigation is broken and several full output-format/ASCII blocks arguably belong in those files rather than inline. Matches 'references present but not clearly signaled; content that should be separate is inline'. Not a 4 because missing referenced files are more than a minor gap; not a 2 because real structure and signaled references are present.

3 / 5

Total

14

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it explicitly covers both what the skill does and when to use it, with multiple concrete actions and natural trigger phrases. It is mostly distinct from other skills, with only minor overlap risk from its broad 'guided understanding' phrasing.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Produces high-level overviews with diagrams, drills into details on request, and offers follow-up exploration questions'), which matches the 'several specific actions; minor gaps' anchor. Not a 5 because the actions are somewhat abstract rather than razor-sharp concrete operations; not a 3 because it clearly enumerates more than 1-2 actions.

4 / 5

Completeness

Explicitly answers both what ('Simulates plan mode with a teaching-first approach... Produces high-level overviews with diagrams, drills into details on request, and offers follow-up exploration questions') and when ('Use when onboarding to a new codebase, exploring architecture, or seeking guided understanding'), with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('onboarding to a new codebase', 'exploring architecture'), matching 'good keyword coverage; a few natural terms missing'. Not a 5 because common synonyms ('codebase tour', 'walk me through', 'code review prep') are absent; not a 3 because coverage is broader than 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

'Simulates plan mode with a teaching-first approach' carves a fairly distinct teaching/onboarding niche, matching 'mostly distinct; minor overlap risk'. Not a 5 because 'guided understanding of any project area' is broad and could overlap with general explanation skills; not a 3 because the framing is clearly more specific than generic document/code helpers.

4 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
0xrabbidfly/eric-cartman
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.