Deception
Forge realistic stand-ins for systems, traffic, and data without misleading actual people.
What This Skill Does
Use this skill to generate believable synthetic artifacts for testing, demos, adversarial exercises, or rehearsal environments. The goal is plausibility under inspection by software and operators, not manipulation of real users or fabrication of evidence.
In this grimoire, Deception is treated as a metaphorical skill with a shipping-now delivery profile.
Canonical reference input: Deception (skill).
When To Use
- You need fake data, demo traffic, or a mock environment that feels operationally real.
- Testing requires a plausible cover story, persona, or artifact without touching production.
- Smoke tests or drills work better when the synthetic inputs resemble actual conditions.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify which signals must look authentic and which markers must remain clearly synthetic.
- Generate the stand-in artifacts and validate them against the target format, workflow, or constraint.
- Return the synthetic set with labeling, isolation rules, and notes on what realism it is simulating.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A realistic synthetic dataset, script, or demo environment brief.
- Notes on the realism targets and what was intentionally faked.
- Isolation and labeling guidance so the artifacts cannot be mistaken for real records.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Never create content meant to impersonate real people, mislead customers, or support fraud.
- Clearly label synthetic artifacts in docs, headers, or test context even when the payload looks real.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/deception create a plausible synthetic version of this scenario for testing or demo use, and label the lines I must not cross
1---2name: deception-23description: Use this skill to generate believable synthetic artifacts for testing, demos, adversarial exercises, or rehearsal environments. The goal is plausibility under inspection by software and operators, not manipulation of real users or fabrication of evidence.4license: CC0-1.05---6# Deception7Forge realistic stand-ins for systems, traffic, and data without misleading actual people.8## What This Skill Does9Use this skill to generate believable synthetic artifacts for testing, demos, adversarial exercises, or rehearsal environments. The goal is plausibility under inspection by software and operators, not manipulation of real users or fabrication of evidence.10In this grimoire, Deception is treated as a metaphorical skill with a shipping-now delivery profile.11Canonical reference input: Deception (skill).12## When To Use1314- You need fake data, demo traffic, or a mock environment that feels operationally real.15- Testing requires a plausible cover story, persona, or artifact without touching production.16- Smoke tests or drills work better when the synthetic inputs resemble actual conditions.1718## Prerequisites1920- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.2122## Procedure23241. Restate the target, the success condition, and any no-touch boundaries before taking action.252. Identify which signals must look authentic and which markers must remain clearly synthetic.263. Generate the stand-in artifacts and validate them against the target format, workflow, or constraint.274. Return the synthetic set with labeling, isolation rules, and notes on what realism it is simulating.285. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.2930## Deliverables3132- A realistic synthetic dataset, script, or demo environment brief.33- Notes on the realism targets and what was intentionally faked.34- Isolation and labeling guidance so the artifacts cannot be mistaken for real records.3536## Pitfalls / Guardrails3738- Keep the metaphor anchored to a real mechanism instead of drifting into lore.39- Never create content meant to impersonate real people, mislead customers, or support fraud.40- Clearly label synthetic artifacts in docs, headers, or test context even when the payload looks real.4142## Verification4344- Check that the result includes every deliverable promised above.45- Check that confirmed facts, assumptions, and inferences are visibly separated.46- Check that the metaphor still maps cleanly to a real operational mechanism.4748## Example Invocation49```text50/deception create a plausible synthetic version of this scenario for testing or demo use, and label the lines I must not cross51```
Hmbown