sred-work-summary

Go back through the previous year of work and create a Notion doc that groups relevant links into projects that can then be documented as SRED projects.

Quality

54%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/sred-work-summary/SKILL.md

Quality

Content

63%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a reasonably well-structured skill for a complex multi-tool workflow that clearly defines the sequence of operations and expected output format. Its main strengths are the clear step-by-step process and explicit output format template. Weaknesses include repetitive ensure blocks, missing concrete MCP/CLI command examples for key operations, and lack of error recovery guidance for what is essentially a large batch data collection operation.

Suggestions

Add concrete `gh` CLI command examples for fetching PRs (e.g., `gh pr list --author=USERNAME --search='created:2024-02-01..2025-01-31' --repo=getsentry/REPO --json title,url,mergedAt`), and show example MCP calls for Notion and Linear queries.

Consolidate the repeated incident filtering logic into a single section or rule rather than restating it three times for GitHub, Notion, and Linear.

Add error handling guidance: what to do if MCP connections fail mid-process, if API rate limits are hit, or if the volume of results exceeds what can be processed in one session.

Consider extracting the output format template and the example Working Summary link into a separate reference file to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary verbosity, such as explaining how to get the current year via a bash command (Claude knows this), and some repetitive 'Ensure' blocks that restate what was already said in the instructions. The incident filtering logic is repeated three times almost identically.	3 / 5
Actionability	The skill provides concrete steps with specific bash commands, clear data collection requirements, and a well-defined output format template. However, it lacks executable examples for MCP interactions and the `gh` CLI commands for fetching PRs, leaving some key execution details to inference.	4 / 5
Workflow Clarity	The workflow is clearly sequenced across 8 steps with logical ordering and some validation checkpoints (e.g., checking if the document already exists, ensuring all links are present). However, there's no explicit error recovery or feedback loop for common failure modes like API rate limits, MCP connection failures, or partial data retrieval, which are likely in a batch operation spanning a full year of data.	4 / 5
Progressive Disclosure	The content is entirely contained in a single file with no bundle files for supporting details. The document format template, the example link, and the detailed step-by-step instructions are all inline. The format template and detailed filtering rules could be split into separate reference files for better organization, though the skill is not excessively long.	3 / 5
	Total	14 / 20 Passed

Description

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

This description reads more like a one-off task instruction than a reusable skill description. It lacks a 'Use when...' clause, uses imperative voice rather than third person, and doesn't comprehensively describe the skill's capabilities or trigger conditions. The SRED-specific focus provides some distinctiveness, but the description needs restructuring to function effectively as a skill selector.

Suggestions

Rewrite in third person descriptive voice (e.g., 'Reviews the previous year of work, groups relevant links into projects, and generates a Notion document for SR&ED (SRED) tax credit documentation.').

Add an explicit 'Use when...' clause with trigger terms like 'SRED', 'SR&ED', 'tax credits', 'R&D documentation', 'CRA', 'scientific research and experimental development'.

Expand the capability description to cover the full scope: what types of work links are reviewed, how projects are grouped, what the Notion doc structure looks like, and whether it handles multiple years or specific formats.

Dimension	Reasoning	Score
Specificity	Names the domain (SRED project documentation) and describes a concrete workflow (reviewing past year's work, grouping links into projects, creating a Notion doc), but it reads more like a single task instruction than a comprehensive list of capabilities.	3 / 5
Completeness	It describes a 'what' (go through past year's work, group links, create Notion doc for SRED projects) but there is no explicit 'when' clause or trigger guidance. The description reads like a task command rather than a skill description, and the missing 'Use when...' clause caps this at 3 per guidelines, but the 'what' is also somewhat vague, bringing it to 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'Notion doc', 'SRED projects', and 'links', but misses natural synonyms and variations users might say such as 'SR&ED', 'tax credits', 'R&D documentation', 'scientific research', or 'CRA'. The term 'SRED' itself is somewhat niche and helpful as a trigger.	3 / 5
Distinctiveness Conflict Risk	The combination of SRED projects, Notion doc creation, and link grouping from past work is fairly distinctive and unlikely to conflict with many other skills. However, it could overlap with general Notion documentation or project documentation skills.	4 / 5
	Total	12 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/sred-work-summary/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.