Acrobatics
Thread complex systems without tripping rate limits, retries, or state.
What This Skill Does
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.
In this grimoire, Acrobatics is treated as a metaphorical skill with a shipping-now delivery profile.
Canonical reference input: Acrobatics (skill).
When To Use
- An integration requires a precise sequence of calls, callbacks, or tokens.
- Concurrency, pagination, or retries can topple the flow if handled clumsily.
- You need a nimble route through constraints rather than more compute.
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.
- Map the sequence, tight constraints, and recovery points before moving.
- Reorder or simplify the path to reduce wasted calls, unstable state, and timing risk.
- Return the stepwise route with checkpoints, balance points, and fallback moves.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A sequenced execution plan for the constrained flow.
- A list of state, timing, and rate-limit risks.
- A compact recovery playbook for dropped or misordered steps.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not mistake unnecessary cleverness for agility; the cleanest path wins.
- Surface hidden coupling and time-sensitive assumptions instead of relying on luck.
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
/acrobatics thread this workflow cleanly through its sequencing constraints and show me the balance points
1---2name: acrobatics-23description: 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.4license: CC0-1.05---6# Acrobatics7Thread complex systems without tripping rate limits, retries, or state.8## What This Skill Does9Use 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.10In this grimoire, Acrobatics is treated as a metaphorical skill with a shipping-now delivery profile.11Canonical reference input: Acrobatics (skill).12## When To Use1314- An integration requires a precise sequence of calls, callbacks, or tokens.15- Concurrency, pagination, or retries can topple the flow if handled clumsily.16- You need a nimble route through constraints rather than more compute.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. Map the sequence, tight constraints, and recovery points before moving.263. Reorder or simplify the path to reduce wasted calls, unstable state, and timing risk.274. Return the stepwise route with checkpoints, balance points, and fallback moves.285. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.2930## Deliverables3132- A sequenced execution plan for the constrained flow.33- A list of state, timing, and rate-limit risks.34- A compact recovery playbook for dropped or misordered steps.3536## Pitfalls / Guardrails3738- Keep the metaphor anchored to a real mechanism instead of drifting into lore.39- Do not mistake unnecessary cleverness for agility; the cleanest path wins.40- Surface hidden coupling and time-sensitive assumptions instead of relying on luck.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/acrobatics thread this workflow cleanly through its sequencing constraints and show me the balance points51```
Hmbown