CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

90%

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

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

An exemplary lean router: the body does exactly what a SKILL.md overview should — orient, then delegate to two clearly labeled, verified one-level-deep references that hold the concrete commands and templates. The only deduction is that the body itself contains no direct task guidance beyond the routing pointers.

DimensionReasoningScore

Conciseness

The 7-line body is entirely lean — one orienting sentence ("Use this skill for docs-site work and docs decision records") and two pointer lines with no padding, no concepts Claude already knows, and no wasted tokens, matching the "every token earns its place" anchor.

5 / 5

Actionability

The pointers are concrete and executable — exact paths ("references/docs-workflow.md", "references/decision-records.md") each with a one-line statement of what they contain — but the body itself is pure routing with no commands or direct task instructions; the executable substance (bun commands, decision template) lives entirely in the referenced files. Per the rubric's instruction-only note the absence of code is not penalized, yet the body stops short of fully covering the tasks themselves, placing it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

This is a simple skill (under 50 lines, single action), and the simple-skill exception applies: the single action — select the matching reference and read it — is unambiguous because each bullet states what it covers ("for docs commands, content rules, and automation" vs "for decisions and ADR-style updates"). No destructive or batch operations are instructed in the body, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references: two bullets, each naming a real bundle file (verified to exist) with its purpose, and the detailed material (commands, rules, templates) is appropriately split into those files. This matches the anchor-5 hub-and-reference structure; the repo files the references point to at runtime are not bundle nesting.

5 / 5

Total

19

/

20

Passed

Description

83%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 description that clearly states what the skill covers and when to use it, with concrete trigger conditions and a helpful exclusion clause. Its main weaknesses are the repetitive generic verb "Work on" and a few missing natural synonyms that would push specificity and trigger coverage to the top anchors.

DimensionReasoningScore

Specificity

Enumerates seven concrete work areas ("Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance"), but every area hangs off the single generic verb "Work on" rather than distinct concrete actions, so it falls just short of the comprehensive anchor 5 and clearly above the 1-2-action anchor 3.

4 / 5

Completeness

Explicitly answers both halves: the "what" is the enumerated list of docs work areas, and the "when" is a concrete trigger clause ("Use for files under docs/, documentation workflows, or requests to record or update a docs decision") reinforced by an exclusion clause ("Do not use for SDK runtime changes unless docs are the main deliverable"). This matches the anchor-5 example's structure; anchor 4's caveat that the 'when' "could be more explicit" does not apply here.

5 / 5

Trigger Term Quality

Includes natural phrases users would say — "changelogs", "docs decisions", "ADR-style records", "files under docs/", "documentation workflows" — giving good keyword coverage, though common variations like "docs site", "documentation update", or "decision record" synonyms are missing, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to a specific project's docs stack (Composio, Fumadocs, the docs/ directory) with an explicit negative boundary for SDK runtime changes, making it mostly distinct; however, "documentation workflows" and general docs-content editing retain minor overlap risk with closely related generic documentation/writing skills, so it is not the minimal-conflict anchor 5.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

ComposioHQ/composio

Path

.agents/skills/docs-decisions/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.