Total Skills
10
Author Profile: z3z1ma
Skills published by z3z1ma with real stars/downloads and source-aware metadata.
Total Stars
110
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
loom-drive
11
Stars
11
Downloads
0
loom-tickets
11
Stars
11
Downloads
0
loom-records
11
Stars
11
Downloads
0
loom-ship
11
Stars
11
Downloads
0
loom-workspace
11
Stars
11
Downloads
0
loom-bootstrap
11
Stars
11
Downloads
0
loom-ralph
11
Stars
11
Downloads
0
loom-evidence
11
Stars
11
Downloads
0
Published Skills
loom-drive
Drive a high-level user objective across multiple Loom phases. Use when the user delegates an outcome that needs objective shaping, owner-record updates, bounded tickets, Ralph/local execution, evidence, critique, reassessment, and continuation without prompting every downstream step.
Repository SourceNeeds Review
loom-tickets
Maintain live execution records and ticket-owned acceptance decisions. Use when new work needs a bounded owner, when execution status, blockers, evidence, critique, route-specific wiki, or retrospective / promotion disposition changes, or when Ralph and other workflow passes must reconcile their consequences into ticket truth.
Repository SourceNeeds Review
loom-records
Shared Loom record grammar: frontmatter, IDs, filenames, typed links, status lifecycles, claim coverage syntax, template use, and native validation patterns. Use when creating or reshaping any Loom artifact, reconciling references, deciding how to name a file, or validating records directly.
Repository SourceNeeds Review
loom-ship
Package already-truthful Loom work for merge, release, or handoff without closing tickets. Use when ticket, evidence, critique, and promotion disposition should become a PR summary, release note draft, risk summary, or follow-up list.
Repository SourceNeeds Review
loom-workspace
Enter a Loom workspace safely: discover structure, bootstrap the tree, resolve ownership, read constitution first, and route to the correct subsystem before downstream work. Use when the next owner layer is unclear, the workspace may be uninitialized, scope looks ambiguous, or you need to decide whether the next move is outer-loop framing, evidence, Ralph execution, critique, wiki, retrospective, or another workflow coordinator.
Repository SourceNeeds Review
loom-bootstrap
Mandatory: use this first in a Loom workspace when Loom doctrine is not already present in the current context. Seeing this skill means Loom is active; read this skill and its ordered references before any work unless an adapter has already loaded the same bootstrap doctrine earlier in the context window.
Repository SourceNeeds Review
loom-ralph
Run the inner implementation loop through bounded fresh-context packets. Use when one exact ticket is Ralph-ready for one explicit implementation iteration and the write boundary, verification posture, source fingerprint, and output contract should be declared up front. For critique or wiki packets, activate the domain skill first and reuse packet discipline there.
Repository SourceNeeds Review
loom-evidence
Maintain observed artifacts and outputs without turning evidence into project-truth ownership. Use when validation output, reproduction steps, test results, screenshots, logs, scan results, red/green output, or other observations need durable preservation with claim-level support or challenge links.
Repository SourceNeeds Review
loom-critique
Run adversarial review as a first-class Loom layer. Use when code changes, behavior changes, Loom records, or other work products need pressure-testing against evidence before acceptance.
Repository SourceNeeds Review
loom-wiki
Maintain the persistent, interlinked explanation layer for accepted understanding. Use when an answer, architecture concept, workflow, troubleshooting pattern, or operator reference should compound into durable knowledge rather than disappear into chat.
Repository SourceNeeds Review