Follow writing-voice for tone.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondocumentationExecute the skills CLI command in your project's root directory to begin installation:
Fetches documentation from epicenterhq/epicenter and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate documentation. Access via /documentation in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
4.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
4.4K
stars
Follow writing-voice for tone.
Documentation explains why, not what. Users can read code to see what it does. They need you to explain the reasoning.
Use this pattern when you need to:
README.md files with architecture intent.Primary job: explain why this folder exists and the mental model.
ls# Converters
Transform field schemas into format-specific representations.
```
┌─────────────┐ ┌──────────────┐
│ Field Schema│────▶│ to-arktype │────▶ Runtime validation
└─────────────┘ ├──────────────┤
│ to-drizzle │────▶ SQLite columns
└──────────────┘
```
Field schemas are pure JSON Schema objects with `x-component` hints. Each converter takes the same input and produces output for a specific consumer.
# Converters
- `to-arktype.ts` - Converts to ArkType
- `to-drizzle.ts` - Converts to Drizzle
- `index.ts` - Exports
The bad example just lists files without explaining the pattern or when to add new converters.
JSDoc explains when and why to use something, not just what it does.
/**
* Get all table helpers as an array.
*
* Useful for providers and indexes that need to iterate over all tables.
* Returns only the table helpers, excluding utility methods like `clearAll`.
*
* @example
* ```typescript
* for (const table of tables.defined()) {
* console.log(table.name, table.count());
* }
* ```
*/
defined() { ... }
/** Returns all table helpers as an array. */
defined() { ... }
@example blocks with realistic usageComments explain why, not what.
// Y.Doc clientIDs are random 32-bit integers, so we can't rely on ordering.
// Use timestamps from the entries themselves for deterministic sorting.
const sorted = entries.sort((a, b) => a.timestamp - b.timestamp);
// Sort the entries
const sorted = entries.sort((a, b) => a.timestamp - b.timestamp);
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
sammcj/agentic-coding
mattpocock/skills
yejinlei/pdf-ocr-skill
yejinlei/pdf-ocr-skill
duc01226/easyplatform
kagurananaga/official-document-writing-skill
documentation reduced setup friction for our internal harness; good balance of opinion and flexibility.
documentation has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added documentation from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in documentation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for documentation matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: documentation is focused, and the summary matches what you get after install.
Registry listing for documentation matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in documentation — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
documentation is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: documentation is focused, and the summary matches what you get after install.
showing 1-10 of 35