CtrlK
BlogDocsLog inGet started
Tessl Logo

writers-pattern

Add a new platform writer module in src/writers/ that generates and writes agent config files for a supported platform. Each writer exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of written file paths. Use when adding platform support for a new agent, integrating a new code AI tool, or extending caliber to support new targets. Do NOT use for modifying existing writers, refactoring scoring logic, or changing how writers are invoked.

77

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is writers-pattern in caliber-ai-org/ai-setup

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-3

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

A high-quality, actionable skill body with executable code, explicit validation checkpoints, and a clear multi-step workflow. Its only gap is progressive disclosure: it is a monolithic single file with no external references to offload the lengthy example and troubleshooting sections.

Suggestions

Move the worked 'Example 1: DevCode platform writer' and the 'Common Issues' troubleshooting entries into a references/ file (e.g. references/examples.md and references/troubleshooting.md), linking to them from the main body to improve progressive disclosure.

Consider extracting the per-platform writer reference snippets (Claude/Cursor/Codex/Copilot line citations) into a references/writer-reference.md so the core Steps stay a concise overview.

Add a one-line 'See references/' navigation block so offloaded detail is clearly signaled at one level deep.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — concrete TypeScript with exact file:line anchors and no padding about what fs/TypeScript/frontmatter are. There is slight overlap between the Critical section and Step instructions, but it reinforces hard constraints rather than restating filler, keeping it at the score-3 anchor.

3 / 3

Actionability

Provides fully executable code (e.g., the complete writeDevcodeConfig writer, the frontmatter template with exact indentation), specific commands ('npm test -- src/writers/__tests__/<platform>.test.ts'), and copy-paste-ready registration blocks — matching the score-3 anchor.

3 / 3

Workflow Clarity

A clearly sequenced six-step process with explicit '**Validation**' checkpoints after nearly every step and fix-and-retry feedback loops (e.g., validation before Step 1, re-validate on failure), matching the score-3 anchor for clear sequence with explicit validation and error-recovery loops.

3 / 3

Progressive Disclosure

No bundle/reference files exist and the skill is a single well-organized file, but at ~260 lines with no external reference links it keeps long worked examples and Common Issues inline that could be split out; the score-2 anchor fits 'structure present but content that should be separate is inline and no clearly signaled one-level-deep references.'

2 / 3

Total

11

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concisely states concrete capabilities, natural trigger conditions, and an explicit exclusion boundary. It clearly answers both what the skill does and when to use it without vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'exports a function that accepts a config interface, creates directories (rules/, skills/, mcp configs), writes files with proper formatting and frontmatter, and returns string[] of written file paths' — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers what ('Add a new platform writer module... generates and writes agent config files') and when ('Use when adding platform support...'), plus a 'Do NOT use' exclusion clause, satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Natural phrasings a user would actually say — 'adding platform support for a new agent, integrating a new code AI tool, or extending caliber to support new targets' — give good coverage of likely trigger language.

3 / 3

Distinctiveness Conflict Risk

Clear narrow niche (adding a writer module) reinforced by an explicit 'Do NOT use for modifying existing writers, refactoring scoring logic, or changing how writers are invoked' boundary that prevents misfiring on adjacent skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
caliber-ai-org/ai-setup
Reviewed

Table of Contents

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.