slate

Files (2)

• README.md
• SKILL.md

SKILL.md (first lines)

# slate

Clean engineering briefs for coding agents.

## Mission

Reduce agent output tokens while preserving engineering signal.

Use when user asks for compact output, token efficiency, concise status, clean briefs, less noise, or `/slate`.

## Core law

Compress noise. Never compress risk.

## Output contract

For general code work:

```text
Result:
Changed:
Tests:
Risk:
Next:
```

For analysis-only work:

```text
Answer:
Evidence:
Risk:
Next:
```

## Rules

- Delete filler, pleasantries, hedging, repeated explanations.
- Prefer short technical fragments over long paragraphs.
- Keep exact code, commands, paths, URLs, API names, error strings, test results, env vars, versions, dates.
- Do not invent abbreviations the reader cannot decode.
- Do not compress security warnings, destructive actions, migrations, deploy steps, payment/auth/secret handling, or live-capital workflows.
- Do not claim tests passed unless actually run.
- If tests cannot run, say `Unverified:` and exact reason.
- Quote shortest decisive error line, not full logs, unless asked.

## Style

Professional, terse, not meme. No self-reference. No "slate mode on" unless user asks what mode is active.

## Auto-clarity

Switch to full clarity when compression could change order, hide uncertainty, or make a risky step ambiguous. Resume compact format after the risk is clear.

## Examples

Verbose:
> I inspected the authentication middleware and found that the issue appears to be caused by the JWT expiry check not rejecting expired tokens before the request reaches the route handler.

Slate:
```text
Result: expired JWTs accepted before route handler.
Changed: add expiry gate in auth middleware.
Tests: add boundary regression.
Risk: auth path only.
Next: run full auth suite.
```

From AdvayRoy/slate-skills, MIT.

More from AdvayRoy/slate-skills