Writing Shape Skill Security Audit
What the author says it does (original text)
Writing, exploit: shape raw material into an article, paragraph by paragraph.
No obvious risks found in this check
- Files checked
- 2
- Risks found
- 0
Inside this skill
The Skill treats a user-provided Markdown file as a source pile, reads it in full, and reshapes it into a separate article; it explicitly says not to edit the source file.
View source
The user has passed (or will pass) a markdown file of raw material. Treat it as the input pile: anything from a tidy list of fragments to a wall of unstructured prose to a transcript. The format does not matter. Read it end-to-end before doing anything else.Then run a shaping session that produces a separate article document. This is **exploit**: the exploring is done, the pile is fixed: commit to a structure and mine the pile to fill it. Do not edit the raw material file: it is read-only to this skill.The writing process is user-guided: the Skill establishes reader prerequisites, offers 2–3 openings for the user to choose from, then discusses and writes the article block by block; the user decides when it is finished.
View source
1. **Read the pile.** Read the input file in full. Form a sense of what's in it.2. **Establish the prerequisites.** Settle with the user what the reader knows walking in: the concepts that are **grounded** from the start. Everything else must be grounded by a block before a later block can lean on it. See [Grounding](#grounding).3. **Draft 2–3 candidate openings.** Each opening should imply a different thesis or angle for the article. Show all of them. Force the user to pick or compose a hybrid. The chosen opening defines what the rest of the article must do.4. **Grow paragraph by paragraph.** After the opening lands, ask "given this opening, what does the reader need to hear next?" Pull material from the pile to answer. The next block may only lean on grounded concepts, and grounds new ones as it lands. Argue about the form the next block takes: a paragraph, a list, a table, a callout, a quote, a code block. Each format choice should be deliberate and defensible.5. **Append to the article file as you go.** Don't batch. Write each agreed paragraph or block immediately so the user can see the article taking shape.6. **Loop step 4 until the article is done.** The user decides when it's done.The Skill makes ongoing changes to the article file, but requires asking for a destination when none is given and rereading the file before each write so intervening user edits are preserved; rewrites are limited to the specified paragraph.
View source
If the user did not say where to save the article, ask once and remember the path.Append to the article file as each block is agreed. Re-read the file from disk before every write: the user may have edited between turns. Never overwrite blindly. If the user wants a paragraph rewritten, edit that specific paragraph in place; leave the rest alone.The configuration disables implicit invocation, so the Skill is intended to be explicitly selected rather than started automatically from conversation content alone.
View source
description: "Writing, exploit: shape raw material into an article, paragraph by paragraph."disable-model-invocation: true--- short_description: "Shape raw material into an article"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
1. **Read the pile.** Read the input file in full. Form a sense of what's in it.2. **Establish the prerequisites.** Settle with the user what the reader knows walking in: the concepts that are **grounded** from the start. Everything else must be grounded by a block before a later block can lean on it. See [Grounding](# …Append to the article file as each block is agreed. Re-read the file from disk before every write: the user may have edited between turns. Never overwrite blindly. If the user wants a paragraph rewritten, edit that specific paragraph in place; leave the rest alone.- Lines read
- 86
- File checksum (to compare versions)
- 4e197ea8d55aef72ab865997422c77c8bf88bd5a90a2ebae36daed1f0487fd75