CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-idea-miner

Mine Claude Code session logs for skill idea candidates. Use when running the weekly skill generation pipeline to extract, score, and backlog new skill ideas from recent coding sessions.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/skill-idea-miner/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, largely executable skill document with concrete commands, a clearly sequenced two-stage pipeline, and properly signaled bundle references. The recurring weaknesses are minor: a missing post-run verification step for the batch backlog merge, slight duplication between Stage 1 and the reference rubric, and inconsistent script paths between sections.

Suggestions

Add an explicit post-run validation step after Stage 2, e.g., "Verify the merge: confirm the backlog's `updated_at_utc` changed and new idea IDs appear before reporting results."

Deduplicate Stage 1's signal-detection bullets by summarizing them in one line and deferring details to `references/idea_extraction_rubric.md`.

Reconcile script paths across sections (the `scripts/run_skill_generation_pipeline.py` reference vs. the `skills/skill-idea-miner/scripts/` paths) so commands are unambiguous from the stated working directory.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence — no space is spent explaining concepts Claude already knows, and the Prerequisites section is a terse checklist. Not a 5 because the intro paragraph restates the description, and the Stage 1 signal-detection bullets plus the two full YAML example blocks (~30 lines of sample output) could be tightened or trimmed.

4 / 5

Actionability

The Quick Start gives copy-paste-ready commands with flags (`mine_session_logs.py --dry-run --output-dir reports/`, `score_ideas.py --candidates ... --backlog ...`) covering the dry-run, full-mining, and scoring cases. Not a 5 because of a minor path gap: "When to Use" references `scripts/run_skill_generation_pipeline.py` while Quick Start uses `skills/skill-idea-miner/scripts/...`, and there is no example showing how the weekly launchd run or its output verification is invoked.

4 / 5

Workflow Clarity

The two stages are clearly sequenced and the `--dry-run` flag serves as an explicit preview checkpoint before the full LLM-scored run, with deduplication thresholds stated concretely ("Jaccard similarity (threshold > 0.5)"). Not a 5 — and held below it as a batch pipeline — because there is no post-merge verification step (e.g., checking the updated backlog, confirming the candidate count) after Stage 2 writes to the shared backlog file.

4 / 5

Progressive Disclosure

Structure is good: the Resources section clearly signals one-level-deep pointers (`references/idea_extraction_rubric.md` — "Signal detection criteria and scoring rubric", plus both scripts), and all referenced files exist in the bundle. Not a 5 because Stage 1's five signal-detection bullets duplicate material that the reference rubric already covers in detail, and the `scripts/tests/` bundle files are never mentioned.

4 / 5

Total

16

/

20

Passed

Description

78%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 with a concrete what, an explicit Use-when clause, and a distinct niche. The main gaps are a slightly narrow trigger condition focused on the weekly pipeline and missing natural synonym variations.

Suggestions

Broaden the Use-when clause to also cover manual/ad-hoc requests, e.g., "or when the user asks to find or prioritize skill ideas from recent sessions".

Add one or two natural synonym phrases (e.g., "skill mining", "idea backlog") to improve trigger coverage.

DimensionReasoningScore

Specificity

"Mine Claude Code session logs for skill idea candidates" and "extract, score, and backlog new skill ideas" name the domain and several concrete actions (mine, extract, score, backlog). Not a 5 because the actions are listed at a high level without enumerating what is scored (novelty, feasibility, value) or what the backlog is for.

4 / 5

Completeness

Both parts are present: the "what" ("Mine Claude Code session logs... extract, score, and backlog new skill ideas") and an explicit "Use when running the weekly skill generation pipeline" clause. Not a 5 because the "when" is narrow — it covers the automated pipeline run but gives no trigger for ad-hoc/manual requests like "find skill ideas in my sessions".

4 / 5

Trigger Term Quality

Natural terms like "skill idea candidates", "session logs", "skill generation pipeline", and "recent coding sessions" are phrases a user of this pipeline would say. Not a 5 because it lacks synonyms and variations (e.g., "skill mining", "idea backlog", "find skill ideas"), and the trigger leans on one narrow pipeline phrase.

4 / 5

Distinctiveness Conflict Risk

"Mine Claude Code session logs for skill idea candidates" occupies a clear niche (session-log mining for skill ideation) with distinct triggers tied to the skill generation pipeline; it is unlikely to fire for unrelated skills. Not lower because the domain and trigger terms are specific enough to avoid meaningful overlap.

5 / 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 possibly missing (scripts/run_skill_generation_pipeline.py)

Warning

Total

15

/

16

Passed

Repository

tradermonty/claude-trading-skills

Path

skills/skill-idea-miner/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.