CtrlK
BlogDocsLog inGet started
Tessl Logo

technical-writing

Write clear, comprehensive technical documentation. Use when creating specs, architecture docs, runbooks, or API documentation. Handles technical specifications, system design docs, operational guides, and developer documentation with industry best practices.

68

1.22x
Quality

54%

Does it follow best practices?

Impact

93%

1.22x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent-skills/technical-writing/SKILL.md
SKILL.md
Quality
Evals
Security

Evaluation results

84%

1%

Notification Service Runbook

Runbook structure and operational content

Criteria
Without context
With context

Service Overview section

100%

100%

Dependencies section

71%

100%

Deployment section with deploy command

100%

100%

Rollback command

100%

100%

Monitoring: request rate metric

0%

40%

Monitoring: error rate metric

100%

100%

Monitoring: latency metric

100%

100%

Common Issues: Symptoms field

100%

100%

Common Issues: Diagnosis field

100%

100%

Common Issues: Resolution field

100%

100%

Troubleshooting log command

100%

100%

Troubleshooting metrics command

57%

71%

Emergency Contacts section

28%

0%

Active voice usage

100%

100%

Numbered steps for procedures

60%

20%

97%

47%

Document the File Processing Pipeline Architecture

Architecture document structure with Mermaid diagrams

Criteria
Without context
With context

Overview section

100%

100%

Architecture Diagram section

0%

100%

Mermaid diagram present

0%

100%

Components: Responsibility

100%

100%

Components: Technology stack

100%

100%

Components: Interfaces

100%

100%

Data Flow section

100%

100%

Key Design Decisions: Context

33%

100%

Key Design Decisions: Options considered

50%

50%

Key Design Decisions: Decision and Rationale

50%

100%

Technology Stack section

40%

100%

Scalability section

100%

100%

Security section

0%

100%

Monitoring and Observability section

20%

100%

Disaster Recovery section

0%

100%

Future Considerations section

0%

100%

Hierarchical headings

100%

100%

100%

5%

Write API Documentation for the Task Management API

API documentation structure and format

Criteria
Without context
With context

Authentication section

100%

100%

Auth curl example with Bearer

60%

100%

Parameters table: Name column

100%

100%

Parameters table: Type column

100%

100%

Parameters table: Required column

100%

100%

Parameters table: Description column

100%

100%

Example Request with curl

100%

100%

Example Response JSON block

100%

100%

Error Responses table

100%

100%

Endpoint method and path format

100%

100%

Code blocks with syntax highlighting

85%

100%

Active voice in prose

100%

100%

Tables for structured data

100%

100%

Consistent structure across endpoints

100%

100%

Short descriptive paragraphs

100%

100%

Repository
supercent-io/skills-template
Evaluated
Agent
Claude Code
Model
Claude Sonnet 4.6

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.