Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

Loslegen

long-sword

Sterne0

Forks0

Aktualisiert11. April 2026 um 22:20

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

Hmbown

Hmbown/mmbnchips

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

name	long-sword
description	Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","metaphorical","direct-fire-and-breach","direct-fire","offense","breach","decisive-action"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Long Sword

Reach past the first layer and cut through to the real target.

What This Skill Does

Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach. In this chip pack, Long Sword is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Long Sword. Hermes shelf: Direct Fire and Breach.

When To Use

The symptom is local but the root cause lives one or more layers deeper in the call chain.
A refactor or fix requires coordinated edits across files that share a common interface or contract.
You need to trace and sever a dependency that extends beyond the current module boundary.

Prerequisites

These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Procedure

Restate the target, success condition, and no-touch boundaries before you spend the chip.
Identify the local surface, then extend reach by tracing imports, callers, or shared types to the true target.
Cut through each layer in order — edit the deepest root first, then propagate the fix outward.
Verify that the extended strike did not leave orphaned references or broken contracts at any layer.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

A coordinated multi-file edit that resolves the root cause, not just the surface symptom.
A map of the reach path: which layers were touched and why the fix could not stay local.

Pitfalls / Guardrails

Keep the metaphor anchored to a real operator move instead of drifting into lore.
Do not use Long Sword when a local Sword cut would suffice — extended reach is for depth, not convenience.
If the fix requires changes across more than three files or modules, consider whether a broader chip is more appropriate.
Never extend reach speculatively; trace the dependency chain first and confirm the true target.
Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

Check that the response includes every promised deliverable and leaves an inspectable audit trail.
Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

/long-sword trace the problem past the local surface and cut through to the root cause: edit the deepest layer that needs to change, then propagate the fix outward, verifying each layer stays intact

Mehr aus diesem Repository

gleiches Repository

black-barrier

Hmbown/mmbnchips

Use Black Barrier when ordinary buffering is too soft and thresholding alone is too permissive. The problem is not just one incoming hit, or a stream of weak noise, but contact that should have to prove itself before it reaches the work at all: ambiguous requests, half-authorized changes, untrusted touchpoints, speculative interruptions, or access that has not earned the right to cross the perimeter. Black Barrier establishes a denser selective shell around a critical surface. Unlike Barrier, it is not a one-hit absorb. Unlike Aura, it does not merely ignore weak impacts below a threshold. It enforces a stricter admission rule: only declared, validated, high-confidence contact gets through, and everything else is refused, deferred, or held outside until it can justify entry.

2026-04-110

curse-shield

Hmbown/mmbnchips

Use Curse Shield when Hermes should protect a surface in a way that makes contact linger on the attacker. The shield is not just there to absorb the next hit or throw an immediate counter; it tags hostile touch with a lasting penalty, mark, or contamination that follows the offender after impact. In practice, Curse Shield is for defended surfaces that impose audit burden, throttling, suspicion, reduced trust, quarantine, follow-up scrutiny, or another durable consequence on whatever keeps pressing into them.

Use Aqua Aura when the real threat is heat: escalating pressure, bursty contention, emotional overtemperature, or rapid-fire noise that is making clean operation impossible. Unlike a plain Aura that simply blanks weaker hits, Aqua Aura diffuses and cools them so Hermes can keep moving without matching the room's panic tempo.

2026-04-110

aura

Hmbown/mmbnchips

Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell.

2026-04-110

Long Sword

Reach past the first layer and cut through to the real target.

What This Skill Does

When To Use

The symptom is local but the root cause lives one or more layers deeper in the call chain.

A refactor or fix requires coordinated edits across files that share a common interface or contract.

You need to trace and sever a dependency that extends beyond the current module boundary.

Prerequisites

These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Procedure

Restate the target, success condition, and no-touch boundaries before you spend the chip.

Identify the local surface, then extend reach by tracing imports, callers, or shared types to the true target.

Cut through each layer in order — edit the deepest root first, then propagate the fix outward.

Verify that the extended strike did not leave orphaned references or broken contracts at any layer.

Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

A coordinated multi-file edit that resolves the root cause, not just the surface symptom.

A map of the reach path: which layers were touched and why the fix could not stay local.

Pitfalls / Guardrails

Keep the metaphor anchored to a real operator move instead of drifting into lore.

Do not use Long Sword when a local Sword cut would suffice — extended reach is for depth, not convenience.

If the fix requires changes across more than three files or modules, consider whether a broader chip is more appropriate.

Never extend reach speculatively; trace the dependency chain first and confirm the true target.

Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

Check that the response includes every promised deliverable and leaves an inspectable audit trail.

Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.

Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

/long-sword trace the problem past the local surface and cut through to the root cause: edit the deepest layer that needs to change, then propagate the fix outward, verifying each layer stays intact