CtrlK
BlogDocsLog inGet started
Tessl Logo

docs-decisions

Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the main deliverable.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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, token-efficient skill body that routes cleanly to two real reference files with clear cues. It loses a little on actionability and workflow clarity because it delegates all detail to references without any post-read sequencing guidance.

Suggestions

Add a brief cue for choosing between the two references (e.g., 'Read docs-workflow.md for editing/building docs; read decision-records.md when recording or updating a decision') to strengthen actionability.

Add a one-line post-read step or checkpoint (e.g., 'After reading, follow the reference's workflow and run its verification command before finishing') to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

The 8-line body is lean and efficient with no over-explanation of concepts Claude already knows; every line routes to a reference or states purpose, matching the score-5 anchor.

5 / 5

Actionability

Gives concrete, specific routing — two real file paths each with a one-line cue ('references/docs-workflow.md for docs commands...', 'references/decision-records.md for decisions...') — but does not state how to choose between them beyond the cue, leaving a minor gap versus fully executable guidance.

4 / 5

Workflow Clarity

As a simple single-purpose skill the single routing action ('Read the relevant reference') is unambiguous and the references are real, but the body does not sequence what to do after reading or include any checkpoint, placing it just below the simple-skill score-5 bar.

4 / 5

Progressive Disclosure

A clear overview points to two well-signaled, one-level-deep references (verified to exist in references/) each with a descriptive cue, yielding easy navigation and appropriate content split per the score-5 anchor.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description that clearly states capabilities, explicit use-conditions, and a negative boundary to avoid misfiring. Slightly product-jargon-heavy in its trigger phrasing, costing one point on trigger-term quality.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance' — giving comprehensive coverage of the domain, matching the score-5 anchor.

5 / 5

Completeness

Explicitly answers 'what' (the capabilities list) and 'when' ('Use for files under docs/, documentation workflows, or requests to record or update a docs decision') with a concrete negative boundary, matching the anchor that requires both with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms like 'docs/', 'documentation workflows', and 'changelogs' plus 'ADR-style records', but leans on product/technical phrasing ('Fumadocs configuration', 'docs automation prompts') and is missing a few common-user phrasings, so it sits between anchors 4 and 5 rather than at 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to Composio docs/Fumadocs with an explicit exclusion ('Do not use for SDK runtime changes unless docs are the main deliverable'), creating a clear niche with minimal conflict risk.

5 / 5

Total

19

/

20

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
ComposioHQ/composio
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.