writing-skills — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited writing-skills (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- From obra/superpowers — no Tessera-specific adaptation needed -->
Writing skills IS Test-Driven Development applied to process documentation.
Write test cases (pressure scenarios), watch them fail (baseline behavior), write the skill, watch tests pass, refactor (close loopholes).
Core principle: If you didn't watch an agent fail without the skill, you don't know if the skill teaches the right thing.
REQUIRED BACKGROUND: Understand test-driven-development before using this skill.
A skill is a reference guide for proven techniques, patterns, or tools.
Skills are: Reusable techniques, patterns, tools, reference guides
Skills are NOT: Narratives about how you solved a problem once
Frontmatter (YAML):
name and descriptionname: letters, numbers, hyphens onlydescription: starts with "Use when...", describes triggering conditions, NOT the skill's workflow---
name: skill-name
description: Use when [specific triggering conditions]
---
# Skill Name
## Overview
Core principle in 1-2 sentences.
## When to Use
Bullet list with symptoms and use cases
## Core Pattern
Before/after comparison or process steps
## Common Mistakes
What goes wrong + fixesDescription = When to Use, NOT What the Skill Does
The description answers: "Should I read this skill right now?" It must NOT summarize the workflow.
# BAD: Summarizes workflow — Claude follows this instead of reading the skill
description: Use when executing plans - dispatches subagent per task with review between tasks
# GOOD: Triggering conditions only
description: Use when executing implementation plans with independent tasks in the current session| TDD Concept | Skill Creation |
|---|---|
| Test case | Pressure scenario with subagent |
| Production code | Skill document (SKILL.md) |
| RED | Agent violates rule without skill (baseline) |
| GREEN | Agent complies with skill present |
| REFACTOR | Close loopholes while maintaining compliance |
NO SKILL WITHOUT A FAILING TEST FIRSTThis applies to new skills AND edits to existing skills.
Tessera-integrated skills: skills/<name>/SKILL.md in the project root.
Personal skills: ~/.claude/skills/<name>/SKILL.md for Claude Code.
RED Phase:
GREEN Phase:
name and description onlyREFACTOR Phase:
Skipping baseline test: You don't know what the skill needs to teach.
Workflow summary in description: Claude reads the description and skips the skill body.
Over-documenting: Target <300 words for frequently-loaded skills.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.