agent-resume-protocol
Skill1 starsChanged 6 days agoLicence not identifiedView on GitHub
Protocol for resuming work after an agent subprocess dies mid-task — detect "continue" signals, reconstruct state from breadcrumb logs, state your inference before acting — plus the habit of logging [intent] breadcrumbs before every slow operation. Use in any hook/cron-spawned agent where turns can be watchdog-killed.
In this repository101 other files it gives its agents.
- skills/react-best-practices/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-skillSkill
- pre-publish-checkSkill
- adversarial-fresh-context-auditSkill
- agent-install-runbookSkill
- agent-kit-hookSkill
- agent-kit-pluginSkill
- agent-kit-policySkill
- agent-memory-mcpSkill
- agent-orchestration-improve-agentSkill
- agent-self-schedulingSkill
- ai-agents-architectSkill
- ai-build-house-rulesSkill
- analyst-house-styleSkill
- assistant-heartbeatSkill
- audio-transcriberSkill
- authority-synthesisSkill
- autonomous-agent-patternsSkill
- begin-taskSkill
- bulletmindSkill
- client-advice-letterSkill
- cloud-account-hardeningSkill
- cloud-cost-guardrailsSkill
- commercial-contract-reviewSkill
- company-thesisSkill
- concise-planningSkill
- contract-anatomySkill
- contract-dispute-analysisSkill
- cqrs-implementationSkill
- daily-brief-exportSkill
- daily-legal-workflow-app-ideasSkill
- dbt-transformation-patternsSkill
- ddd-context-mappingSkill
- ddd-strategic-designSkill
- ddd-tactical-patternsSkill
- decision-log-keepingSkill
- deferred-work-registerSkill
- effective-agent-skillsSkill
- efficient-web-researchSkill
- evening-wrapSkill
- event-store-designSkill
- form-croSkill
- frontend-designSkill
- frontend-developerSkill
- gainers-trackingSkill
- gemini-deep-researchSkill
- hedera-consensus-serviceSkill
- hedera-token-serviceSkill
- incident-runbookSkill
- internal-commsSkill
- investor-profile-templateSkill
- launchagent-schedulingSkill
- legal-research-memoSkill
- legal-writing-editorSkill
- litigation-hold-and-triageSkill
- macro-readthroughSkill
- mcp-builderSkill
- mediation-prepSkill
- meeting-reminderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

