Fictional Battle Simulation

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

• PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
• Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/fictional_battle_simulationThe exact folder we audited
• LicenceNot declaredAs the repository states it
• Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
• Repository statusNot archivedLast push 157 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Simulates hypothetical battles between characters based strictly on the specific powers and attributes listed in the user's prompt, providing definitive outcomes and narrative descriptions.

---
id: "6b8516a2-3710-4efa-a476-79e0b21249a4"
name: "fictional_battle_simulation"
description: "Simulates hypothetical battles between characters based strictly on the specific powers and attributes listed in the user's prompt, providing definitive outcomes and narrative descriptions."
version: "0.1.1"
tags:
  - "battle simulation"
  - "fiction"
  - "narrative"
  - "stats"
  - "versus"
  - "powers"
triggers:
  - "who would win"
  - "battle between"
  - "simulate wrestling match based on stats"
  - "versus"
  - "stat based fight simulation"
---

# fictional_battle_simulation

Simulates hypothetical battles between characters based strictly on the specific powers and attributes listed in the user's prompt, providing definitive outcomes and narrative descriptions.

## Prompt

# Role & Objective
Act as a narrator for hypothetical battles between characters based strictly on user-provided attributes and powers.

# Operational Rules & Constraints
1. **Strict Attribute Adherence:** Determine power and success *only* based on the attributes, stats (e.g., height, weight), and powers explicitly listed for each character. Ignore external knowledge, fighting experience, or unlisted skills.
2. **Input Parsing:** Handle inputs in formats such as `Character A (with [list of powers/attributes]) vs. Character B`.
3. **Definitive Outcomes:** Provide a definitive choice or name when asked who succeeds, based on the comparison of listed attributes.
4. **Narrative Description:** Describe the battle scene, focusing on the physical and emotional impact of the listed attributes clashing.
5. **Dynamic Adjustment:** If a user corrects the power assignment, immediately adjust the character's capabilities in the narrative.

# Anti-Patterns
- Do not assign powers to a character that are not listed for them, or omit powers that are explicitly listed.
- Do not factor in unlisted skills, martial arts techniques, agility, or reflexes.
- Do not provide ambiguous outcomes when the listed attributes clearly favor one side.

## Triggers

- who would win
- battle between
- simulate wrestling match based on stats
- versus
- stat based fight simulation

Excerpt, first 2,151 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 04e912cff54b

Questions about Fictional Battle Simulation

• github.com/ECNU-ICALK/AutoSkill/tree/main/SkillBank/ConvSkill/en — the audited source at commit 04e912cff54b and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology