scribe

Technical writer - documentation, README, guides

Quality

63%

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/scribe/SKILL.md

Quality

Content

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

The content delivers useful, mostly actionable documentation templates with clean organization, but it is padded with generic placeholders and presents principles rather than a sequenced writing workflow with verification steps.

Suggestions

Replace generic placeholder template lines ('Feature 1', 'Brief description...') with concise structural annotations so tokens teach structure rather than fill space.

Add a short sequenced documentation workflow with a verification checkpoint, e.g. draft -> review against code -> sync API examples -> validate links.

Consider moving the full README/architecture templates into a references/ file and keeping SKILL.md as an overview pointing to them.

Dimension	Reasoning	Score
Conciseness	The body is mostly templates rather than fluff, but the README and architecture templates carry generic placeholder content (e.g., 'Feature 1', 'Brief description of what this project does') that pads tokens without adding guidance beyond structure.	3 / 5
Actionability	It provides concrete, copy-paste-ready templates (README structure, JSDoc API example, architecture doc skeleton) covering common documentation cases, with only minor gaps.	4 / 5
Workflow Clarity	The 'Writing Guidelines' section lists principles (Clarity, Examples, Structure) rather than a sequenced process, and there are no validation checkpoints for reviewing or syncing docs with code.	3 / 5
Progressive Disclosure	The single file is well-organized into Documentation Types and Writing Guidelines with clear section headers and no nested references, though some templates could live in separate reference files.	4 / 5
	Total	14 / 20 Passed

Description

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

The description is a concise third-person noun phrase that names the domain and a few deliverable types, but it lacks an explicit 'when to use' trigger clause and broader keyword coverage. It reads as a label rather than a discovery-friendly trigger.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when writing or revising READMEs, API docs, architecture docs, or user guides.'

Expand trigger terms with natural synonyms users say, such as 'docs', '.md files', 'changelog', 'API reference', 'getting started guide'.

Reframe deliverables as concrete actions ('writes, structures, and revises documentation') to raise specificity.

Dimension	Reasoning	Score
Specificity	Phrases like 'documentation, README, guides' name the domain and a couple concrete deliverable types, but they are nouns rather than concrete actions and coverage is not comprehensive.	3 / 5
Completeness	It gives a clear 'what' (technical writer for documentation/README/guides) but no explicit 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'documentation' and 'README' are natural terms a user might say, but common variations and synonyms (e.g., docs, .md, API docs, changelog) are missing.	3 / 5
Distinctiveness Conflict Risk	The scope is somewhat specific (documentation, README, guides) but still broad enough to overlap with general writing or code-comment skills.	3 / 5
	Total	12 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: TurnaboutHero/oh-my-antigravity
Path: skills/scribe/SKILL.md
Commit: f73e1ff

Reviewed: 15 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.