scribe

Technical writer - documentation, README, guides

Quality

37%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/scribe/SKILL.md

Quality

Discovery

22%

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 is too terse and lacks actionable detail. It identifies a domain (technical writing) and lists document types but fails to specify what actions the skill performs or when Claude should select it. The absence of concrete verbs and explicit trigger guidance makes it difficult for Claude to confidently choose this skill over alternatives.

Suggestions

Add specific actions the skill performs, e.g., 'Creates, structures, and maintains technical documentation including READMEs, API docs, and user guides'

Include a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to write documentation, create a README, draft technical guides, or improve existing docs'

Expand trigger terms to include variations like 'docs', 'technical writing', 'API documentation', 'user manual', 'CONTRIBUTING.md'

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language ('documentation, README, guides') without specifying concrete actions like 'write', 'edit', 'structure', or 'format'. It names document types but not what the skill actually does with them.	1 / 3
Completeness	Missing both clear 'what' (no actions specified) and 'when' (no 'Use when...' clause or equivalent trigger guidance). The description only lists document types without explaining capabilities or selection criteria.	1 / 3
Trigger Term Quality	Contains some relevant keywords users might say ('documentation', 'README', 'guides') but misses common variations like 'docs', 'technical docs', 'API documentation', 'user manual', or 'how-to'.	2 / 3
Distinctiveness Conflict Risk	Somewhat specific to technical writing domain, but 'documentation' and 'guides' are broad enough to potentially conflict with API documentation skills, code commenting skills, or general writing skills.	2 / 3
	Total	6 / 12 Passed

Implementation

52%

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

This skill provides solid, actionable templates for common documentation types with good concrete examples. However, it lacks workflow guidance on how to approach documentation tasks, when to use each template, and how to validate documentation quality. The persona framing and closing quote waste tokens without adding value.

Suggestions

Add a workflow section explaining when to use each documentation type and how to approach documentation tasks (e.g., 'For new projects: start with README, then add API docs as you build')

Remove the persona introduction ('You are Scribe') and closing quote to improve token efficiency

Add validation checkpoints such as 'verify all public APIs are documented' or 'check that examples are runnable'

Include guidance on documentation maintenance workflow - how to keep docs in sync with code changes

Dimension	Reasoning	Score
Conciseness	The skill provides useful templates but is somewhat verbose. The templates themselves are valuable, but the persona framing ('You are Scribe') and the closing quote add unnecessary tokens. The templates could be more condensed.	2 / 3
Actionability	Provides fully concrete, copy-paste ready templates for README, API documentation, and architecture docs. The examples are complete and executable with realistic structure and syntax.	3 / 3
Workflow Clarity	No workflow or process is defined. The skill provides templates but no guidance on when to use each, how to approach documentation tasks, or any sequencing for creating documentation. The 'Writing Guidelines' are vague principles, not actionable steps.	1 / 3
Progressive Disclosure	Content is organized into clear sections by documentation type, but everything is inline in one file. For a documentation skill, references to detailed guides (e.g., API doc standards, README best practices) would improve navigation. The structure is reasonable but could benefit from better organization.	2 / 3
	Total	8 / 12 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: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 24 days 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.