CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

project-discovery

Analyze course transcript files (.srt) to discover teachable projects. Use when you need to scan a course folder and identify what hands-on projects are taught, without generating any code. Outputs a manifest file that can be used later for selective project generation. Triggers on phrases like "discover projects", "analyze course", "find projects in transcripts", "what projects are in this course".

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-discovery/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 highly actionable, well-sequenced discovery procedure whose main weaknesses are redundancy and missing output validation. The duplicated schema examples and inlined reference content inflate token cost without adding information, and the batch workflow lacks a verify-before-complete checkpoint.

Suggestions

Delete the 'Output' section's full JSON examples and keep one canonical manifest example (Step 5), deferring the complete schema to references/manifest-schema.md — this alone removes ~50 duplicated lines.

Add a validation step between Step 5 and Step 7: re-read project-findings.json to confirm it parses and that len(projects) + len(skipped_srts) accounts for every SRT discovered in Step 2, before marking progress.json complete.

Trim the in-body 'Project Identification Signals' and 'Project State Transitions' heuristics to a short summary and point to references/discovery-patterns.md, keeping the body as an overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and action-oriented (e.g., 'Read each SRT file **in sorted order**', the exact `find . -name "*.srt" -type f | grep -v "CODE/" | sort` command), but the 'Output' section (~lines 37–88) fully duplicates the progress.json and project-findings.json schemas already shown in Steps 1, 5, and 7 — the manifest JSON appears three times and progress.json four times, with inconsistent example dates (2024 vs 2025). The tech-stack table listing React, Vue, Django, etc. also restates technologies Claude already knows.

3 / 5

Actionability

Guidance is copy-paste ready throughout: an exact bash command for locating SRTs, complete JSON templates for every output state (projects found, none found, interrupted run), a field-by-field manifest table, an enforced naming pattern ('Pattern: `Project_[Framework][CoreFeature][Distinguisher]`' with worked examples like 'Job Portal' → `Project_JobPortal`), and a verbatim report template. Common cases including the no-projects edge case are all covered.

5 / 5

Workflow Clarity

The 7-step sequence is clearly ordered with strong restart semantics ('If status is "started": Previous run was interrupted. Clean up any partial `CODE/__CC_Projects/` folder and restart') and correct write-ordering (manifest before marking complete). However, this is a batch operation (50+ SRT files, 'Preparing for batch processing of multiple courses') with no validation/verification step — nothing checks the manifest is valid JSON or that `projects` + `skipped_srts` account for all discovered files — which caps workflow clarity at 3 per the rubric's batch-operation rule.

3 / 5

Progressive Disclosure

Both referenced files exist and are one level deep with a dedicated 'Reference Files' section ('`discovery-patterns.md` - Detailed patterns for identifying projects', '`manifest-schema.md` - Complete JSON schema'), but the body inlines the very content those files cover: full manifest schemas appear twice in the body despite manifest-schema.md existing, and detailed start/continue/end/skip heuristics duplicate discovery-patterns.md's 'Project Start Indicators'. This matches the anchor where content that should be separate is inline alongside present-but-underused references.

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 answers what, when, and how it's triggered with natural user phrases and a clear negative boundary. The only gaps are minor: a few missing trigger synonyms and the slightly broad 'analyze course' phrase.

DimensionReasoningScore

Specificity

It names the domain precisely ('course transcript files (.srt)') and lists several concrete actions in third person — analyze transcripts to discover projects, scan a course folder, output a manifest for selective generation — plus an explicit negative boundary ('without generating any code'). Not a 5 because capabilities the body claims (complexity classification, tech-stack detection) go unmentioned, and 'discover teachable projects' / 'identify what hands-on projects are taught' restate one action.

4 / 5

Completeness

Both halves are explicit: the 'what' ('Analyze course transcript files (.srt) to discover teachable projects... Outputs a manifest file that can be used later for selective project generation') and the 'when' ('Use when you need to scan a course folder and identify what hands-on projects are taught') reinforced with concrete trigger phrases — matching the top anchor's structure exactly.

5 / 5

Trigger Term Quality

Natural trigger phrases are explicit and user-shaped: 'discover projects', 'analyze course', 'find projects in transcripts', 'what projects are in this course', and the file extension (.srt) is included. Falls short of 5 because common variations like 'catalog projects', 'list the projects', or 'which projects does this course teach' are not covered.

4 / 5

Distinctiveness Conflict Risk

The .srt course-transcript niche is clear and 'without generating any code' explicitly separates it from the sibling project-generation skill. Not a 5 because 'analyze course' is a broad phrase a user might say when wanting a general course summary, creating minor overlap risk with other course-analysis 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-discovery/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.