skill-context-packet
Skill1 starsChanged 8 months agoMITView on GitHub
Use when the next turn needs a minimum context packet rather than a full root or subtask state refresh.
In this repository6 other files it gives its agents.
- skill-context-keeperSkill
- skill-governanceSkill
- skill-handoff-summarySkill
- skill-phase-gateSkill
- skill-subtask-contextSkill
- skill-task-continuitySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this package when the next root or subtask turn needs a compact packet instead of a full state file.
- Distinctive: line 11
Keep the package boundary narrow: compress the minimum context object for the next turn without taking over root-state refresh, …
≈ “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.
Files
Skill Context Packet
Overview
Use this package when the next root or subtask turn needs a compact packet instead of a full state file. Keep the package boundary narrow: compress the minimum context object for the next turn without taking over root-state refresh, subtask-state refresh, workflow gates, or handoffs.
Use This Skill When
- the next turn only needs a small packet of facts, constraints, and exact next action
- a root or subtask state file is getting too large to inject directly
- you want to hand a bounded task slice to another owner without copying the full history
- you need a packet-first workflow that protects context budget
Do Not Use This Skill When
- the root task or subtask state itself needs a full refresh
- the task needs a risky-change checkpoint or phase gate
- the work is pausing and needs a handoff summary
- the repo needs suite bootstrap or routing guidance
Package Boundary
This package owns packet compression such as .agent-state/root/PACKET.md or .agent-state/subtasks/<slug>/PACKET.md.
It does not own root task state, does not own workflow gates, and does not own final handoffs.
References
README.mdandREADME.zh-CN.md: entry docs and direct invocation wordingreferences/use-cases.md: positive and negative trigger examplesreferences/prompt-templates.en.md: reusable packet-writing promptsassets/PACKET.template.md: packet template
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.

