Project-local operational knowledge for THIS app, accumulated by prior operator runs. Covers app surfaces (routes, ports, processes, admin overlays), auth/login flow, db state management, common UI flows, and known footguns. Use whenever the operator agent needs project-specific operating knowledge — read at session start, update before submitting.
EnglishRuntime mental model, agent boundaries, and workflow patterns for the sisyphus multi-agent orchestration…
EnglishAuthor new sisyphus agents, sub-agents, hooks, skills, and orchestrator modes. Use when extending sisyphus runtime behavior — adding a domain-specific agent variant, project-level hook, custom orchestrator phase, or shared skill. Covers what to put in each file, why, and which extension to reach for.
EnglishForensic debugging of a past sisyphus multi-agent session — reconstruct what the orchestrator and each agent could see at each decision point and judge whether their calls were reasonable. Use when asked to debug, autopsy, or explain a sisyphus session: a failure, wasted cycles, a weird decision, a stalled agent, or how a session succeeded. Takes a session ID/name or a path to a session dir or exported dump.
EnglishIncludes Sisyphus Authoring, Sisyphus Autopsy, and other workflows.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Operator
Project-local operational knowledge for THIS app, accumulated by prior operator runs. Covers app surfaces (routes, ports, processes, admin overlays), auth/login flow, db state management, common UI flows, and known footguns. Use whenever the operator agent needs project-specific operating knowledge — read at session start, update before submitting.
Sisyphus
Runtime mental model, agent boundaries, and workflow patterns for the sisyphus multi-agent orchestration system
Sisyphus Authoring
Author new sisyphus agents, sub-agents, hooks, skills, and orchestrator modes. Use when extending sisyphus runtime behavior — adding a domain-specific agent variant, project-level hook, custom orchestrator phase, or shared skill. Covers what to put in each file, why, and which extension to reach for.
Sisyphus Autopsy
Forensic debugging of a past sisyphus multi-agent session — reconstruct what the orchestrator and each agent could see at each decision point and judge whether their calls were reasonable. Use when asked to debug, autopsy, or explain a sisyphus session: a failure, wasted cycles, a weird decision, a stalled agent, or how a session succeeded. Takes a session ID/name or a path to a session dir or exported dump.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Operator skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.