Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

arcana

Estrellas98

Forks12

Actualizado5 de abril de 2026, 03:15

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Hmbown

Hmbown/Wizards-of-the-Ghosts

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	arcana
description	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.
version	1.0.0
author	Wizards of the Ghosts
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["skill","shipping-now","metaphorical","investigation-and-preparation","analysis","discovery","translation","preflight"]}}

Arcana

Apply deep technical knowledge to understand how systems work under the hood.

What This Skill Does

When To Use

A technical system needs to be understood at a level deeper than its documentation provides.
You need to explain how something actually works — not what it claims to do, but what it does.
A debugging or architecture question requires knowledge of underlying mechanisms, not just surface APIs.

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 the system, protocol, or technology to analyze.
Explain the mechanism at the appropriate depth: not the marketing version, but how it actually works.
Surface non-obvious implications, edge cases, or failure modes that follow from the mechanism.
Deliver the explanation with a clear note on what is documented fact vs. observed behavior vs. inference.
Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

A mechanistic explanation of how the system actually works under the hood.
Non-obvious implications or edge cases that follow from the mechanism.
A confidence note: what is documented, what is observed, and what is inferred.

Pitfalls / Guardrails

Keep the metaphor anchored to a real mechanism instead of drifting into lore.
Do not confuse documentation with behavior. The docs say what it should do; arcana reveals what it does.
Clearly separate established knowledge from speculation when reasoning about undocumented behavior.

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

/arcana explain how this [system/protocol/technology] actually works under the hood, beyond what the documentation says

Más de este repositorio

mismo repositorio

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

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

animal-friendship

Hmbown/Wizards-of-the-Ghosts

Animal Friendship is the first-contact spell for unfamiliar APIs, vendors, and services. It treats integration work as relationship-building: learn the temperament, respect the boundaries, and earn a stable exchange before asking for anything ambitious. The goal is not domination but trustable cooperation.

2026-04-0598

name	arcana
description	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.
version	1.0.0
author	Wizards of the Ghosts
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["skill","shipping-now","metaphorical","investigation-and-preparation","analysis","discovery","translation","preflight"]}}

Arcana

Apply deep technical knowledge to understand how systems work under the hood.

What This Skill Does

When To Use

A technical system needs to be understood at a level deeper than its documentation provides.
You need to explain how something actually works — not what it claims to do, but what it does.
A debugging or architecture question requires knowledge of underlying mechanisms, not just surface APIs.

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 the system, protocol, or technology to analyze.
Explain the mechanism at the appropriate depth: not the marketing version, but how it actually works.
Surface non-obvious implications, edge cases, or failure modes that follow from the mechanism.
Deliver the explanation with a clear note on what is documented fact vs. observed behavior vs. inference.
Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

Deliverables

A mechanistic explanation of how the system actually works under the hood.
Non-obvious implications or edge cases that follow from the mechanism.
A confidence note: what is documented, what is observed, and what is inferred.

Pitfalls / Guardrails

Keep the metaphor anchored to a real mechanism instead of drifting into lore.
Do not confuse documentation with behavior. The docs say what it should do; arcana reveals what it does.
Clearly separate established knowledge from speculation when reasoning about undocumented behavior.

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

/arcana explain how this [system/protocol/technology] actually works under the hood, beyond what the documentation says