write-docs

Authoring Fern MDX documentation pages for the Opik docs site, plus release-note and changelog routing. Use when writing or updating pages under apps/opik-documentation/documentation/fern/, drafting PR descriptions, or picking the right changelog surface.

Quality

88%

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

Quality

Content

77%

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

A comprehensive, actionable docs skill with strong templates and verification loops, weakened mainly by repetition of prohibitions and a monolithic structure with no reference files split out.

Suggestions

Consolidate the repeated prohibitions (no inline H1, don't infer paths from folder layout, docs.yml is read-only) into the single "Forbidden and discouraged" section and reference it once elsewhere instead of restating each 2–3 times.

Move the Fern MDX component catalog and/or changelog routing details into a references/ file (e.g. COMPONENTS.md, CHANGELOG_ROUTING.md) and link to them from SKILL.md to improve progressive disclosure.

Trim the "Style and voice" page-shape guidance to a tighter bulleted reference, keeping only what is not already implied by the v1 anchor files.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept-padding Claude already knows, but key prohibitions are repeated three times ("no inline # H1", "don't infer paths from folder layout", "docs.yml is read-only") and could be tightened.	2 / 3
Actionability	Provides copy-paste-ready frontmatter, routing YAML, MDX component examples, and verification commands — all concrete and executable.	3 / 3
Workflow Clarity	"Where new pages live" and "Local verification" give clearly sequenced steps with explicit validation checkpoints (confirm frontmatter renders, components resolve, links work, images load).	3 / 3
Progressive Disclosure	Well-organized into clear sections, but everything lives in one monolithic SKILL.md with no split-out reference bundle files; the component catalog and changelog details could be separated.	2 / 3
	Total	10 / 12 Passed

Description

100%

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, third-person description that pairs concrete capabilities with an explicit "Use when" trigger clause and a distinctive niche. It covers what, when, and which surfaces without padding.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "Authoring Fern MDX documentation pages", "release-note and changelog routing", "drafting PR descriptions" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (authoring Fern MDX pages + changelog routing) and when via an explicit "Use when" clause with concrete triggers.	3 / 3
Trigger Term Quality	Includes natural phrasings a user would say ("writing or updating pages", "drafting PR descriptions", "picking the right changelog surface") alongside the repo path anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to a clear niche (Opik Fern docs site + changelog surfaces) with distinct triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 4 suspicious	Warning

	Total	15 / 16 Passed

Repository: comet-ml/opik
Path: .agents/skills/write-docs/SKILL.md
Commit: aae4650

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