Name: sred-project-organizer
Rating: 54.400000000000006 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

sred-project-organizer

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

70%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, validated multi-step workflow with concrete, actionable guidance for an MCP-driven Notion/Linear/GitHub process. Its main weakness is that the referenced bundle files (SRED.md, project-template.md) do not actually exist, breaking progressive disclosure.

Suggestions

Add the missing `references/SRED.md` and `references/project-template.md` bundle files so the referenced paths resolve.

De-duplicate the uncertainty-length constraint (stated in both Step 4 and Step 5) and consolidate the repeated user-review checkpoints.

Name the specific MCP tools or `gh` commands expected (e.g. which Notion MCP tool creates a child page) to close the small actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient for a complex workflow, but it repeats constraints (the "only a few sentences long" uncertainty-length rule appears in both Step 4 and Step 5) and reiterates the user-review checkpoint at multiple sub-steps, which could be tightened.	3 / 5
Actionability	Guidance is concrete and specific — exact Notion document names ("SRED Project Summary - <year> <project name>"), named sections to fill, explicit 100-word limits, and a referenced template — leaving only minor gaps around the actual MCP tool invocations.	4 / 5
Workflow Clarity	The process is clearly sequenced (Step 1-6 with Step 5 sub-steps 1-8) and includes explicit validation via "Ensure:" checklists, user review checkpoints, and a feedback loop ("Make any changes they ask for"), satisfying the batch-operation validation requirement.	5 / 5
Progressive Disclosure	References to `${CLAUDE_SKILL_ROOT}/references/SRED.md` and `project-template.md` are clearly signaled and one level deep, but the `references/` directory does not exist, so the referenced bundle files are missing and navigation dead-ends.	3 / 5
	Total	15 / 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 conveys what the skill does and targets a distinctive niche, but it lacks an explicit "when to use it" trigger clause and relies on a single generic action verb. It is functional but would benefit from added trigger guidance and more specific action wording.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when preparing SRED (Scientific Research and Experimental Development) project submissions from a year's worth of project work.'

Replace the single generic verb 'organize' with several concrete actions, e.g. 'classify projects as SREDable, draft project descriptions and technical uncertainties, and assemble a submission-ready Notion document.'

Include natural trigger synonyms users would say, such as 'SRED claim', 'SR&ED submission', or 'scientific research and experimental development'.

Dimension	Reasoning	Score
Specificity	The description names the domain ("SRED format", "projects and their related documentation") and one concrete action ("organize them into the SRED format for submission"), but offers only a single generic verb ("organize") rather than multiple specific actions.	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 trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	It includes the distinctive term "SRED" plus "projects", "documentation", and "submission", but provides no common variations or synonyms and no natural trigger phrasing a user would actually say.	3 / 5
Distinctiveness Conflict Risk	The "SRED format" niche is highly specific and unlikely to conflict with unrelated skills, but the closely related `sred-work-summary` skill referenced in the body creates minor overlap risk, keeping this just below 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 57c135b

Reviewed: 16 hours ago

Table of Contents

Discovery Implementation Validation

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.