Security audit
Security checks for vulnerabilities and agentic risk
This prompt-writing skill is mostly documentation, but it asks the agent to keep persistent personal prompting memory and includes unsafe prompt-priority advice.
Review this skill before installing. Use it only if you are comfortable with a local ~/prompting folder storing style notes, corrections, and prompt history, and periodically inspect or delete those files. Treat any advice about user messages overriding system prompts as incorrect.
This pattern attempts to override system instructions or ignore safety constraints. Without LLM analysis, manual review is recommended.
- Benefits from "Let's think step by step"
- More tolerant of verbose prompts
- JSON mode available and reliable
- User message can override system
- Good at creative variation
**Works well:** Chain-of-thought, detailed examples
The phrase 'In user message: Can override system prompt' directly instructs prompt override behavior, which is a classic jailbreak-enabling pattern. Even if intended as prompting advice, it can be reused to attempt circumvention of safety or policy instructions, making it materially risky in a document about prompt engineering techniques.
- **Start of prompt:** Sets overall behavior
- **End of prompt:** Last thing model "remembers"
- **Both:** For critical constraints
- **In user message:** Can override system prompt
## Output Anchoring
Start the assistant response:
The skill explicitly directs storage of prompt history, user voice, and learned corrections under the user's home directory, but provides no consent, minimization, retention, or deletion guidance. Because these files may contain sensitive personal writing samples, preferences, and prior interactions, they create a real privacy and data-retention risk if accessed by other tools, users, or future sessions.
The instruction to store writing style, preferred models, and past corrections in ~/prompting/memory.md encourages persistent collection of potentially sensitive personal content without any user-facing warning. Writing samples and corrections can reveal identity, habits, or confidential material, so silent retention increases privacy exposure beyond the immediate task.
Persistently logging natural-language preferences and corrections creates a durable record that can accumulate sensitive contextual information over time. Even if intended for personalization, this retained free-text memory may later be exposed, repurposed, or queried in ways the user did not expect, making the risk contextually meaningful in a prompting skill that handles user-authored content.
This section explicitly teaches that placing constraints in the user message can override higher-priority instructions, which normalizes prompt-priority confusion and can enable instruction-bypass behavior. In a prompting skill, that guidance is more dangerous because readers may operationalize it to defeat system safeguards or policy controls in other contexts.
Line L48 gives a language-specific instruction, "Translate this to Spanish," as a generic prompting example. Because the policy forbids forcing a specific language without user opt-in or justification, this natural-language example can be read as endorsing a fixed locale choice without any indication that the user selected it.
No suspicious patterns detected.