CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sred-project-organizer

Take a list of projects and their related documentation, and organize them into the SRED format for submission.

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/sred-project-organizer/SKILL.md

The canonical home for this skill is sred-project-organizer in administrakt0r/AI-Agents-Safe-Coding-Skills

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, actionable procedural skill: the multi-step workflow has explicit user-validation checkpoints, feedback loops, and per-step checklists, with detail correctly deferred to reference files. The main weaknesses are the confusing nested step numbering inside Step 5, minor duplicated instructions, and reliance on reference files that could not be verified in the bundle.

Suggestions

Relabel the sub-steps within Step 5 (currently "Step 1"-"Step 8", which collides with top-level step names) to something like "5.1"-"5.8" so the hierarchy is unambiguous.

Deduplicate repeated instructions: state the Uncertainty-length constraint and the review-checkpoint pattern once and reference them, or move the Work Summary format template into a reference file.

Add a short worked example of one completed "SRED Project Summary" child document to make the expected output fully concrete.

DimensionReasoningScore

Conciseness

The body is purely procedural with no explanations of concepts Claude already knows, and the "Ensure" checklists earn their tokens. It falls short of lean/efficient (5) due to small redundancies: the Uncertainty-length constraint is stated twice (sub-steps 4 and 5 of Step 5), and the "provide the link and ask the user to review" phrasing repeats across three places.

4 / 5

Actionability

The instruction-only guidance is mostly executable: exact document names ("SRED Project Descriptions", "SRED Project Summary - <year> <project name>"), reference template paths, word limits ("no more than 100 words"), and an inline Work Summary format template. Minor gaps keep it from 5: no example of a completed project summary and no concrete guidance on creating child Notion docs via MCP.

4 / 5

Workflow Clarity

The top-level sequence (Steps 1-6) is clear with explicit validation checkpoints (Step 3 list confirmation, user review gates in sub-steps 3 and 8), feedback loops ("Make any changes they ask for"), and "Ensure" checklists, so the batch-operation cap at 3 does not apply. It misses 5 because the sub-steps inside Step 5 are also labeled "Step 1" through "Step 8", colliding with the top-level step numbering and creating navigation confusion.

4 / 5

Progressive Disclosure

Detailed material (SRED project criteria, the Notion project template) is appropriately split into clearly-signaled, one-level-deep references (${CLAUDE_SKILL_ROOT}/references/SRED.md and references/project-template.md), and the body stays overview-level. However, the referenced files are not present in the provided bundle to verify, and the inlined Work Summary format template in Step 1 arguably belongs in a reference file.

4 / 5

Total

16

/

20

Passed

Description

53%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 clearly states what the skill does and anchors itself to the distinctive SRED domain, but it lacks any 'Use when...' trigger guidance and misses natural keyword variations, leaving it serviceable but below the standard of the good examples.

Suggestions

Add an explicit trigger clause, e.g. "Use when preparing a SRED/SR&ED (Scientific Research and Experimental Development) tax credit submission or organizing projects into SRED format."

Include the common spelling and synonyms users would naturally say, such as "SR&ED" and "tax incentive program", to improve trigger term coverage.

Mention the concrete outputs and sub-actions (classifying SREDable projects, creating Notion project summaries) to raise specificity from one action to several.

DimensionReasoningScore

Specificity

"Take a list of projects and their related documentation, and organize them into the SRED format for submission" names the domain (projects/documentation, SRED) and one concrete action (organize into SRED format), matching the 'names domain and 1-2 concrete actions' anchor. It is not a 4 because it does not list several specific actions, and not a 2 because 'organize into the SRED format for submission' is domain-specific rather than generic.

3 / 5

Completeness

The 'what' is clearly stated (organize projects into the SRED format for submission), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is clear, not vague.

3 / 5

Trigger Term Quality

The description includes the niche keyword "SRED" plus "projects", "documentation", and "submission", but misses common variations users would naturally say such as "SR&ED", "tax credit", or "Scientific Research and Experimental Development". This matches the 'some relevant keywords but missing common variations or synonyms' anchor rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

"SRED" is a distinctive niche term with minimal conflict risk, but the generic phrase "Take a list of projects and their related documentation" leaves minor overlap risk with general project-organization skills, and the absence of explicit trigger phrases prevents a 5.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/sred-project-organizer/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.