Writing Beats Skill Security Audit
What the author says it does (original text)
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
No obvious risks found in this check
- Files checked
- 2
- Risks found
- 0
Inside this skill
This Skill defines an interactive writing workflow: establish the audience's prior knowledge, propose 2–3 candidate beats from user-provided material, and write a beat to the article file only after the user selects it.
View source
1. **Establish the prerequisites.** Before any beats, settle with the user what the audience already knows walking in: the concepts that are **grounded** from the start. Everything else must be grounded by a beat before a later beat can use it. See [Grounding](#grounding).2. Write 2–3 candidate **starting beats**, drawn from the raw material. Each is a different entry point into the article. Each may only lean on grounded concepts; note what new concepts each one grounds. Show the user the beats before writing to the article file. The user picks one. Preview what beats that pick unlocks, as if the user is seeing a little way down the path.3. Once the user picks a starting beat, write **only that beat** to the article file. A beat may be one sentence or several paragraphs, whatever that beat naturally is. Stop there.4. Re-read the article file from disk. Then offer 2–3 candidate **next beats**: different directions the journey could pivot to from where the article now stands. Each must be reachable from the current grounded set; note what each one grounds.It makes ongoing changes to the user-designated article file: it rereads the file before every write to preserve user edits, and may edit an existing beat in place when the user explicitly requests a rewrite.
View source
If the user did not say where to save the article, ask once and remember the path.- Append one beat at a time. Never write ahead.- Re-read the article file from disk before every write. Preserve user edits absolutely.- If the user edits a previous beat substantially, let it change what comes next.- If the user says "rewrite that beat" or "go back and try a different beat 3", do it: edit in place, leave the rest alone.The Skill disallows implicit invocation, and its metadata also disables model invocation, so it is intended to require explicit user activation.
View source
description: Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.disable-model-invocation: true--- short_description: "Assemble raw material into beats"policy: allow_implicit_invocation: falseFiles and check records2 files
Coverage and gaps
Content covered in each file
These are the source ranges included in this check, not a guarantee that every issue has been resolved.
SKILL.mdFull text includedagents/openai.yamlFull text included
This report is for the version above. We read the available code and instructions without running the skill or checking extra packages it installs. This is not a promise of safety: a different version or setup may behave differently.
SKILL.mdInstructionsagents/openai.yamlSupporting file
Operations mentioned in code and instructions
Read files
3. Once the user picks a starting beat, write **only that beat** to the article file. A beat may be one sentence or several paragraphs, whatever that beat naturally is. Stop there.4. Re-read the article file from disk. Then offer 2–3 candidate **next beats**: different directions the journey could pivot to from where the article now stands. Each must be reachable from the current grounded set; note what each one grounds.5. Loop steps 3–5 until the article reaches a natural end.- Append one beat at a time. Never write ahead.- Re-read the article file from disk before every write. Preserve user edits absolutely.- If the user edits a previous beat substantially, let it change what comes next.- Lines read
- 74
- File checksum (to compare versions)
- 11105882a1414a17e05395e757685a6b884e74e9baba8fe96eab64c64a7d223f