CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-generator

Generate complete, working code projects from course transcript analysis. Use when you have a project specification (from discovery or manual input) and need to create all implementation files, documentation, and configuration. Triggers on phrases like "generate project", "create project from transcript", "build the project", "generate Project_XxxYyy".

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/project-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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.

A well-structured, mostly lean body with concrete output locations, mode-detection strings, and file manifests, but it is held back by two systemic gaps: no validation/verification step in a batch file-generation workflow, and two large bundle reference files that are completely orphaned from the SKILL.md navigation. Linking the references and adding a post-generation check would lift the two weakest dimensions substantially.

Suggestions

Add a validation checkpoint to both workflows, e.g. after generating files run a build/install check ('npm install' then typecheck) and fix-and-retry before finishing — batch file creation currently has no verification loop.

Add a '## References' section pointing to the bundle files, e.g. '**Code patterns**: See [code-patterns.md](references/code-patterns.md)' and '**File templates**: See [file-templates.md](references/file-templates.md)', so the 1,400+ lines of existing templates and patterns are actually discoverable and loaded.

In chunked mode, make the consistency check explicit as a step (e.g. 're-read one already-generated file to match import style and naming before writing new files') so cross-chunk consistency is a checkpoint rather than an implicit expectation.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — no concept explanations, just concrete directives like 'Use proper imports even for files not yet created' and 'Add TODO comments for parts in later chunks'. It is not 5 because of redundancy: the H1 line, 'Purpose', and 'When to Use' sections restate the frontmatter description and each other, and 'Capabilities' overlaps the later mode/guideline sections. It is well above 3 since the padding is limited to restated framing rather than unnecessary explanation.

4 / 5

Actionability

For an instruction-only skill the guidance is concrete: exact output path '{course_path}/CODE/__CC_Projects/{ProjectName}/', literal detection strings for chunked mode ('Chunk X of Y', 'Architecture Spec (Reference)'), a specific file manifest, and a full example output tree. It is not 5 because the actual code patterns and file templates live in references/code-patterns.md and references/file-templates.md yet are never pointed to, leaving the 'how' of code generation to general knowledge; it stays above 3 because the body's specifics (paths, filenames, indicators, ordering rules) go well beyond high-level hints.

4 / 5

Workflow Clarity

Both modes have clear numbered sequences ('1. Read all provided transcript content... 4. Create documentation'; chunked mode adds 5 rules), so steps are coherent — but there are no validation checkpoints, matching the anchor 'steps listed but validation gaps'. Generating an entire project is a batch operation, and the rubric caps workflow clarity at 3 when batch workflows lack verification steps (e.g., 'verify the project compiles/installs' or a fix-and-retry loop); 'Don't recreate files in the Already Generated list' is a guard, not output validation.

3 / 5

Progressive Disclosure

The body itself is well-sectioned and appropriately lean, and content is genuinely split into separate bundle files — but references/code-patterns.md (825 lines) and references/file-templates.md (584 lines) are never mentioned anywhere in SKILL.md, so references are present in the bundle yet not signaled at all. This matches the anchor 'references present but not clearly signaled'; it is not 2 because the body has solid structure with no monolithic inline bloat, and not 4 because a reader of SKILL.md alone would never discover or load the two most detailed resources.

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.

A strong description that explicitly states both what the skill does and when to use it, with an explicit set of natural trigger phrases. The main weaknesses are trigger breadth (missing common variations) and file-category-level action descriptions rather than the skill's fuller capabilities.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'Generate complete, working code projects from course transcript analysis' and 'create all implementation files, documentation, and configuration' — matching the anchor for several specific actions with minor gaps. It falls short of 5 because the actions stay at the file-category level and omit capabilities like transcript parsing, tech-stack adherence, or chunked mode that the skill actually has; it clears 3 because more than 1-2 concrete actions are named.

4 / 5

Completeness

It clearly answers 'what' ('Generate complete, working code projects from course transcript analysis... create all implementation files, documentation, and configuration') and 'when' ('Use when you have a project specification... Triggers on phrases like...') with concrete trigger phrases, exactly matching the anchor-5 pattern. It is not 4 because the 'when' clause is fully explicit with enumerated triggers rather than merely present-but-imprecise.

5 / 5

Trigger Term Quality

It provides explicit natural trigger phrases — 'generate project', 'create project from transcript', 'build the project', 'generate Project_XxxYyy' — that users would plausibly say, giving good keyword coverage. It is not 5 because common variations like 'scaffold', 'implement', or 'write the code for the project' are missing, and 'Project_XxxYyy' is a naming convention rather than natural speech; it exceeds 3 because multiple natural phrases are included rather than just relevant-but-generic keywords.

4 / 5

Distinctiveness Conflict Risk

The 'course transcript analysis' context and the 'Project_XxxYyy' convention carve out a mostly distinct niche with minor overlap risk against generic code-generation or scaffolding skills. It is not 5 because triggers like 'build the project' and 'generate project' are generic enough to collide with a general project-scaffolding skill; it is above 3 because the transcript-based framing is specific and unlikely to fire for unrelated skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

KennethJefferson/cc_skill_ProjectSynth

Path

.claude/skills/project-generator/SKILL.md

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.