Updated 2w ago
by rlaope
ultraprompt
Fable 5.1 solution tracing. Prompting skills so Opus, Sonnet, Haiku, Grok, Gemini and open-weight models work like Fable 5.1
34 GitHub stars (34)
+2 in 16 days
| Period | New stars |
|---|---|
| Oct 1 | 0 |
| Oct 2 | 0 |
| Oct 3 | 0 |
| Oct 4 | 0 |
| Oct 5 | 0 |
| Oct 6 | 0 |
| Oct 7 | +1 |
| Oct 8 | 0 |
| Oct 9 | 0 |
| Oct 10 | 0 |
| Oct 11 | 0 |
| Oct 12 | 0 |
| Oct 13 | 0 |
| Oct 14 | +1 |
| Oct 15 | 0 |
| Oct 16 | 0 |
- 12 skills (12 skills found in its SKILL.md files)
- 5 forks (5 forks)
- 2w ago last update (Last updated 2w ago)
Install
Skills CLI
npx skills add rlaope/ultraprompt
Asks which skills and agents to install. Just one: npx skills add rlaope/ultraprompt --skill context-memory-hygiene — add -g for every project.
Claude Code
git clone https://github.com/rlaope/ultrapromptcp -r "ultraprompt/skills/context-memory-hygiene" ~/.claude/skills/
Copies the context-memory-hygiene skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add rlaope/ultraprompt
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md.
-
context-memory-hygiene
Invoke when deciding what to load into context, what to persist across turns or sessions, and what to drop — reads only what the task needs, writes durable handoffs, avoids context pollution, and chooses when to re-derive versus recall.
skills/context-memory-hygiene/SKILL.md on GitHub (opens in a new tab) -
delegation-parallelism
Invoke when deciding whether to split work across parallel agents/sessions or do it inline — tests scope independence, weighs coordination cost against the parallelism win, and sets an observation cadence for delegated work.
skills/delegation-parallelism/SKILL.md on GitHub (opens in a new tab) -
exploration-strategy
Build an accurate mental model of an unfamiliar codebase or problem before making any edit — structural scan, entry-point location, one end-to-end trace, and an explicit known-vs-assumed ledger.
skills/exploration-strategy/SKILL.md on GitHub (opens in a new tab) -
failure-mode-enumeration
Systematically enumerate how code can break — boundaries, concurrency, partial failure, malicious input, time, resource exhaustion — before writing defenses, then convert the list into tests and guards while pruning paranoia that does not pay rent.
skills/failure-mode-enumeration/SKILL.md on GitHub (opens in a new tab) -
honest-reporting
Invoke when writing any status, completion, or result report — calibrates claims to the evidence actually gathered, marks the unmeasured as open, reports failures plainly, and distinguishes "verified at layer X" from "should work".
skills/honest-reporting/SKILL.md on GitHub (opens in a new tab) -
hypothesis-management
Debug by maintaining 2-4 competing hypotheses with explicit evidence and kill criteria, choosing each probe to maximally discriminate between them instead of confirming a favorite.
skills/hypothesis-management/SKILL.md on GitHub (opens in a new tab) -
incremental-safety
Decompose a large or risky change into a sequence of independently safe intermediate states, so the system stays green at every step and any step can be reverted alone.
skills/incremental-safety/SKILL.md on GitHub (opens in a new tab) -
self-correction-loop
Invoke when an implementation attempt produces a failure signal (test failure, compile error, wrong output, crash, perf regression) and you must decide whether to retry, rethink, or back out — instead of hammering the same fix.
skills/self-correction-loop/SKILL.md on GitHub (opens in a new tab) -
spec-to-code-fidelity
Invoke when implementing from an authoritative written source — an RFC, academic paper, binary format spec, protocol document, or mathematical derivation — where correctness means matching the document, not just passing ad-hoc tests.
skills/spec-to-code-fidelity/SKILL.md on GitHub (opens in a new tab) -
state-probing
Invoke before acting on any assumption about the runtime or environment — versions, running processes, file/disk reality, git state, network reachability. Grounds claims about the world in a cheap probe instead of a guess, and re-probes when state may have gone stale.
skills/state-probing/SKILL.md on GitHub (opens in a new tab) -
tradeoff-articulation
Invoke when a design decision has multiple viable implementations and the choice affects performance, memory, complexity, or blast radius — forces enumerating real alternatives, quantifying the axes that matter, and recording what would reverse the decision.
skills/tradeoff-articulation/SKILL.md on GitHub (opens in a new tab) -
verification-discipline
Invoke before claiming any task is done — defines what counts as evidence of completion (execution, not inspection) and how to verify at the layer the requirement actually lives at.
skills/verification-discipline/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.