Skip to content
Back to skills

writer-self-editing-checklist

ASecurity

SELF-EDITING CHECKLIST — extracted from roles.json deepPrompt for writer

  • 8 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added May 27, 2026
data-aidocumentation

Security analysis

A100/100

Pro scans all 11 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add iampantherr/SecureContext --skill skills --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of writer-self-editing-checklist?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for writer-self-editing-checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/iampantherr-writer-self-editing-checklist/badge)](https://www.skillsdirectory.com/skills/iampantherr-writer-self-editing-checklist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
id: writer-self-editing-checklist@1@global
name: writer-self-editing-checklist
version: 1
scope: global
description: SELF-EDITING CHECKLIST — extracted from roles.json deepPrompt for writer
intended_roles: [writer]
mutation_guidance: |
  This skill encodes a behavioral procedure originally embedded in the
  writer role's deepPrompt. When mutating, preserve the imperative
  voice and the numbered/bulleted structure. Sub-rules within a numbered
  point can be edited; the top-level numbering should not change without
  operator approval (it's referenced by other skills + role text).
tags: [writer, role-extracted, v0-19-bootstrap]
acceptance_criteria:
  min_outcome_score: 0.6
  completes_in_seconds: 600
---
# SELF-EDITING CHECKLIST

_(Extracted from `roles.json` deepPrompt for the **writer** role during the v0.19.0 role/skill split. Original content preserved verbatim. Edit freely; the mutator will propose improvements based on skill_runs telemetry once this skill is invoked by an agent.)_

---

Before submitting any documentation:
- Is every pronoun's antecedent unambiguous?
- Does every step in a procedure tell the reader what success looks like?
- Are all code examples tested in a clean environment?
- Is every term used consistently throughout?
- Are all prerequisites stated before they are required?
- Does every heading make sense out of context?
- Are there any passive-voice constructions where the actor matters?
- Is any content duplicated from another source that should be canonical?
- Will every link still resolve in six months?
- Does this document know its Divio type and stay inside it?

---

Files in this skill

  • _staging_v0_19/_REPORT.md32.8 KB
  • _staging_v0_19/_role_account-executive.slimmed-deepprompt.md2.8 KB
  • _staging_v0_19/_role_account-manager.slimmed-deepprompt.md2.8 KB
  • _staging_v0_19/_role_accountant.slimmed-deepprompt.md2.7 KB
  • _staging_v0_19/_role_analyst.slimmed-deepprompt.md5 KB
  • _staging_v0_19/_role_architect.slimmed-deepprompt.md2.8 KB
  • _staging_v0_19/_role_blogger.slimmed-deepprompt.md2.6 KB
  • _staging_v0_19/_role_board-advisor.slimmed-deepprompt.md2.7 KB
  • _staging_v0_19/_role_brand-architect.slimmed-deepprompt.md2.7 KB
  • _staging_v0_19/_role_brand-designer.slimmed-deepprompt.md2.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…