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.
74
62%
Does it follow best practices?
Impact
93%
1.02xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent-skills/docs-site-writing/SKILL.mdDeveloper API endpoint reference page
What endpoint does — first
100%
100%
When it is called section
100%
100%
Request example present
100%
100%
Response shape documented
100%
100%
Consistent json code fences
100%
100%
HTTP method in prose or standalone
100%
100%
Developer tone precision
100%
100%
Short introduction
100%
100%
Specific scannable headings
80%
70%
Correct admonition type
100%
100%
User guide with tone and structure
Short introduction
100%
100%
Page structure order
100%
100%
Second person used
100%
100%
User docs tone
40%
70%
Prerequisites before steps
50%
37%
Limitations near relevant step
62%
100%
Correct admonition type
100%
87%
Short admonitions
100%
100%
Specific scannable headings
75%
87%
Consistent App Connect terminology
100%
100%
No engineering jargon in user content
25%
50%
Caveats in main prose
100%
100%
Solutions page with business value and MkDocs Material patterns
Business value leads
100%
100%
Short introduction
100%
100%
Concrete claims
100%
100%
Anchored in App Connect capabilities
100%
100%
Card grid or comparison table
100%
100%
Markdown button for CTA
100%
100%
Approachable tone
100%
100%
Consistent App Connect terminology
100%
100%
Specific scannable headings
80%
80%
No repo-internal conventions
100%
90%
f59d4a2
Table of Contents
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.