docs-site-writing

Use this skill when writing or revising content inside `rc-unified-crm-extension/docs` for the App Connect MkDocs site. Follow the existing public docs style used across user, developer, solution, and support pages, while applying modern documentation best practices for clarity, structure, scannability, and correctness.

1.02x

Quality

—

Does it follow best practices?

Impact

93%

1.02x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

77%

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

The body delivers concrete, actionable style guidance with a sequenced workflow and an explicit review checklist, but it is a single inline file with no progressive disclosure and some redundant voice guidance.

Suggestions

Split reference-like material (MkDocs Material patterns, admonition guidance, API/interface page template) into a reference file linked from SKILL.md to enable one-level-deep progressive disclosure.

Merge the overlapping voice guidance across Goal, Existing House Style, and Things to Avoid to remove redundancy and tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and assumes Claude knows how to write, but the Goal, Existing House Style, and Things to Avoid sections overlap in voice guidance, so it could be tightened.	2 / 3
Actionability	Concrete, specific guidance throughout: numbered section ordering, per-area style rules, named admonition types with use cases, an API page template, and good/bad heading examples give copy-applicable instruction.	3 / 3
Workflow Clarity	A clear sequence runs from the First Step (inspect 2-3 nearby pages) through structured writing to an explicit Review Checklist that verifies the page before finishing.	3 / 3
Progressive Disclosure	Sections are well-organized and scannable, but the ~180-line skill uses no reference files at all and keeps reference-like material (MkDocs patterns, admonition guidance, API template) fully inline, so it does not meet the one-level-deep reference bar.	2 / 3
	Total	10 / 12 Passed

Description

75%

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 clearly answers what the skill does and when to use it with an explicit trigger and a distinct, path-bound niche, though its action list is high-level and trigger phrasing is somewhat tied to an internal path.

Suggestions

List a couple more concrete actions beyond "writing or revising" (e.g. structuring pages, adding admonitions, fixing scannability) to lift specificity.

Add common natural-language variations a user might say ("update", "edit", "write documentation for App Connect") alongside the path-bound trigger.

Dimension	Reasoning	Score
Specificity	It names the domain and two actions ("writing or revising content") but does not enumerate multiple specific concrete actions, so it sits at the domain-and-some-actions level rather than a comprehensive list.	2 / 3
Completeness	An explicit "Use this skill when writing or revising content inside..." clause states when to use it, and the rest states what it does (follow existing docs style while applying best practices), satisfying both what and when.	3 / 3
Trigger Term Quality	Relevant keywords like "writing", "revising", "docs", and "documentation" appear, but the trigger is bound to the internal path `rc-unified-crm-extension/docs` and omits common variations a user might say (e.g. "update", "edit pages").	2 / 3
Distinctiveness Conflict Risk	Scoping to the App Connect MkDocs site at `rc-unified-crm-extension/docs` and explicitly excluding the repo-level internal `docs/` folder gives it a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ringcentral/rc-unified-crm-extension
Commit: 25fc4c6

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