Run any Skill in Manus with one click

faerie-fire

Stars98

Forks12

UpdatedApril 5, 2026 at 03:15

Faerie Fire marks things that are already known. It does not search, discover, explain, translate, or fix. The user has already identified what matters; your job is to make those items impossible to overlook by annotating, tagging, highlighting, or visually surfacing them in context.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Hmbown

Hmbown/Wizards-of-the-Ghosts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	faerie-fire
description	Faerie Fire marks things that are already known. It does not search, discover, explain, translate, or fix. The user has already identified what matters; your job is to make those items impossible to overlook by annotating, tagging, highlighting, or visually surfacing them in context.
user-invocable	true

Faerie Fire

Make hidden things visible by highlighting, tagging, and marking them for attention.

Overview

Faerie Fire is interpreted here as a metaphorical spell with a shipping-now execution model.

Canonical source: Faerie Fire (spell)

Provider target: OpenClaw

When To Use

"Highlight", "tag", "mark", "annotate", "call out", "flag" applied to specific items the user has already named or located
"Make X visible" where X is a known set of findings, clauses, functions, tickets, or features
"Show me where [specific thing] appears" — location surfacing, not discovery
"Annotate", "add margin notes", "color-code", "produce a summary table of marked items"
The user provides the target list and asks you to apply markers to a document, codebase, dataset, or diagram

Workflow

Confirm the target set: Restate what the user wants marked. If the list is implicit, extract it explicitly before annotating.
Choose the marking strategy based on the medium:
Code: inline comments, // HIGHLIGHT: markers, or extracted function lists with file:line references
Documents: bold/underline, margin notes, or a findings table with clause references
Data/tables: tagged rows, conditional formatting descriptions, or filtered views
Diagrams: callout labels, numbered annotations, or a legend mapping marks to gaps
Apply markers with context: Every mark must include why the item was flagged, not just that it was flagged. A marker without rationale is noise.
Deliver two artifacts: the annotated source and a concise summary listing what was marked and the selection criteria.

Deliverables

An annotated version of the source material with key findings highlighted and marked.
A summary of what was highlighted and why each item warrants attention.

Guardrails

Be selective. Highlighting everything is highlighting nothing. If the user gives you 200 items, ask them to narrow or apply a ranking.
Never claim to have discovered something you were not asked to mark. Faerie Fire illuminates; it does not hunt.
If the request mixes marking with fixing, translating, or explaining, scope yourself to marking only and note the boundary.
Do not use for: Scanning/searching: "Find all hidden webhooks", "Scan for MCP servers" — the user is asking you to discover, not mark. Use a detection spell instead.
Do not use for: Explaining: "Explain what this manifest does", "What does this code do?" — comprehension, not annotation.
Do not use for: Translating: "Translate from German to English" — language conversion, not highlighting.
Do not use for: Rewriting: "Rewrite for executives", "Simplify this report" — transformation, not marking.
Do not use for: Fixing: "Highlight the risky parts and fix them" — Faerie Fire only marks; it does not remediate. Decline the fix portion or route it to a separate spell.
Do not use for: Vague requests: "Highlight the important stuff" with no criteria — ask the user what "important" means before proceeding.

Default Invocation

Use $faerie-fire to highlight the most important [findings/patterns/elements] in this [document/codebase/dataset] so they cannot be overlooked.

More from this repository

same repository

mage-hand

Hmbown/Wizards-of-the-Ghosts

Use this skill for small, careful remote manipulations where dexterity matters more than force.

2026-04-0598

unseen-servant

Hmbown/Wizards-of-the-Ghosts

Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.

2026-04-0598

arcana

Hmbown/Wizards-of-the-Ghosts

In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.

2026-04-0598

mirage-arcane

Hmbown/Wizards-of-the-Ghosts

In D&D, Mirage Arcane goes beyond Hallucinatory Terrain — the illusory terrain actually has substance. You can walk on illusory bridges, feel illusory walls. The real-world version is the deep simulation: digital twins, high-fidelity synthetic environments, test harnesses so realistic that systems under test cannot distinguish them from production. Mirage Arcane is the most dangerous illusion because its power is in being indistinguishable from reality. That same power makes it the most useful for stress testing, training, and scenario planning — but it requires the strongest labeling discipline.

2026-04-0598

project-image

Hmbown/Wizards-of-the-Ghosts

In D&D, Project Image creates an illusory copy of yourself at a distant location — you can see through its eyes, speak through its mouth, and cast spells through it. The real-world version is remote presence: avatars, recorded video stand-ins, bot representations, asynchronous video messages. Project Image is the spell for being in two places at once — attending a meeting via avatar while working on something else, leaving a recorded presence in a channel, or deploying an automated representative that speaks with your voice and authority within defined limits.

2026-04-0598

acrobatics

Hmbown/Wizards-of-the-Ghosts

Use this skill when the work is a choreography problem: brittle sequencing, async handoffs, or constrained flows that must stay upright end to end. It shines on API dances, dependency ordering, and recovery logic where grace matters more than brute force.

2026-04-0598

name	faerie-fire
description	Faerie Fire marks things that are already known. It does not search, discover, explain, translate, or fix. The user has already identified what matters; your job is to make those items impossible to overlook by annotating, tagging, highlighting, or visually surfacing them in context.
user-invocable	true

Faerie Fire

Make hidden things visible by highlighting, tagging, and marking them for attention.

Overview

Faerie Fire is interpreted here as a metaphorical spell with a shipping-now execution model.

Canonical source: Faerie Fire (spell)

Provider target: OpenClaw

When To Use

"Highlight", "tag", "mark", "annotate", "call out", "flag" applied to specific items the user has already named or located
"Make X visible" where X is a known set of findings, clauses, functions, tickets, or features
"Show me where [specific thing] appears" — location surfacing, not discovery
"Annotate", "add margin notes", "color-code", "produce a summary table of marked items"
The user provides the target list and asks you to apply markers to a document, codebase, dataset, or diagram

Workflow

Confirm the target set: Restate what the user wants marked. If the list is implicit, extract it explicitly before annotating.
Choose the marking strategy based on the medium:
Code: inline comments, // HIGHLIGHT: markers, or extracted function lists with file:line references
Documents: bold/underline, margin notes, or a findings table with clause references
Data/tables: tagged rows, conditional formatting descriptions, or filtered views
Diagrams: callout labels, numbered annotations, or a legend mapping marks to gaps
Apply markers with context: Every mark must include why the item was flagged, not just that it was flagged. A marker without rationale is noise.
Deliver two artifacts: the annotated source and a concise summary listing what was marked and the selection criteria.

Deliverables

An annotated version of the source material with key findings highlighted and marked.
A summary of what was highlighted and why each item warrants attention.

Guardrails

Be selective. Highlighting everything is highlighting nothing. If the user gives you 200 items, ask them to narrow or apply a ranking.
Never claim to have discovered something you were not asked to mark. Faerie Fire illuminates; it does not hunt.
If the request mixes marking with fixing, translating, or explaining, scope yourself to marking only and note the boundary.
Do not use for: Scanning/searching: "Find all hidden webhooks", "Scan for MCP servers" — the user is asking you to discover, not mark. Use a detection spell instead.
Do not use for: Explaining: "Explain what this manifest does", "What does this code do?" — comprehension, not annotation.
Do not use for: Translating: "Translate from German to English" — language conversion, not highlighting.
Do not use for: Rewriting: "Rewrite for executives", "Simplify this report" — transformation, not marking.
Do not use for: Fixing: "Highlight the risky parts and fix them" — Faerie Fire only marks; it does not remediate. Decline the fix portion or route it to a separate spell.
Do not use for: Vague requests: "Highlight the important stuff" with no criteria — ask the user what "important" means before proceeding.

Default Invocation

Use $faerie-fire to highlight the most important [findings/patterns/elements] in this [document/codebase/dataset] so they cannot be overlooked.