communication-style-09086f — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited communication-style-09086f (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.
Be extremely concise. Sacrifice grammar for concision.
| Instead of | Write |
|---|---|
| "The user will be able to..." | "User can..." |
| "This component is responsible for..." | "Handles..." |
| "In order to achieve this, we need to..." | "Requires:" |
| "It should be noted that..." | (delete) |
Use:
Every output follows this order:
1. Brief overview (2-3 sentences MAX)
2. Main content (tables, bullets, diagrams)
3. Unresolved questions (if any)
4. Numbered action steps (ALWAYS LAST)Action steps appear last because terminal output is read bottom-up -- the most important content occupies the most visible position.
## Next Steps
1. Create auth module at src/auth/
2. Add JWT dependency
3. Implement login endpoint
4. Add testsBefore action steps, list unresolved questions:
## Unresolved Questions
- OAuth provider preference? (Google, GitHub, both)
- Session duration requirement?
- Rate limiting needed?Catches ambiguities before they become bugs.
| Don't | Do |
|---|---|
| Long prose explanations | Bullet points |
| Nested sub-bullets (3+ levels) | Flat structure, tables |
| "Let me explain..." | (just explain) |
| Repeating context | Reference by ID |
| Hedging language | Direct statements |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.