CtrlK
BlogDocsLog inGet started
Tessl Logo

team-prd

Read and update the team's shared PRD in the team-prd AFS workspace. Trigger when the user asks about current/inflight/done work, wants to start a new work item, mark something complete, or add an open question to the team's spec. Enforces per-dev subdir isolation to avoid write conflicts between multiple developers' agents.

99

1.02x
Quality

100%

Does it follow best practices?

Impact

99%

1.02x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 tight, actionable workflow doc: concrete paths and formats, clearly sequenced multi-step processes with read-before-write checkpoints, and clean single-file organization with no token waste. No substantive weaknesses to address.

DimensionReasoningScore

Conciseness

Lean imperatives and short lists throughout; the only explanatory prose (the opening rationale for the layout) conveys non-obvious context Claude would not already know, so every token earns its place rather than padding.

3 / 3

Actionability

Gives exact paths (e.g. '/inflight/<handle>/<slug>.md', '/done/<YYYY-MM-DD>-<slug>.md') and concrete format blocks for questions and revised-section markers; as an instruction-only skill, the absence of code is not penalized because the guidance is specific and actionable.

3 / 3

Workflow Clarity

Three numbered workflows (start, mark-done, add-question) are clearly sequenced, with pre-write checkpoints — re-reading shared files and scanning /inflight/ for conflicts before starting — acting as validation; the single low-risk destructive step (deleting the inflight file after copying to /done/) is guarded by these read-heavy reflexes.

3 / 3

Progressive Disclosure

A single well-organized file with clear sections and no nested/deep references; no bundle files exist and nothing in the content needs splitting, so well-organized sections suffice for a top score.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, well-formed description: it names concrete actions, gives explicit natural-language triggers, answers both 'what' and 'when', and occupies a clearly distinct niche. No substantive weaknesses to address.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Read and update the team's shared PRD', 'start a new work item', 'mark something complete', 'add an open question' — matching the score-3 anchor rather than the score-2 anchor that names only a domain and some actions.

3 / 3

Completeness

Explicitly states what it does ('Read and update the team's shared PRD') and when to use it ('Trigger when the user asks about...'), satisfying both halves with an explicit trigger clause; uses imperative/third-person voice with no first/second person.

3 / 3

Trigger Term Quality

'asks about current/inflight/done work, wants to start a new work item, mark something complete, or add an open question' covers the natural phrasings a user would say, exceeding the score-2 anchor that misses common variations.

3 / 3

Distinctiveness Conflict Risk

The 'team-prd AFS workspace' niche and 'per-dev subdir isolation' framing give it a clear, distinct scope unlikely to trigger for the wrong skill.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
redis/agent-filesystem
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.