act
Skill16 starsChanged 7 months agoMITView on GitHub
Reads recent session context, infers what you were working on, and proposes the specific next action. Use when resuming after a break, or say "act" / "what should we do next" / "pick up where we left off". Executes immediately on confirmation.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- petr-korobeinikov/skillstheir own version, first seen Nov 8, 2026
- gabrielkoerich/skillstheir own version, first seen Nov 1, 2026
- fore-vip/skillstheir own version, first seen Sep 4, 2026
- apideck-libraries/api-skillstheir own version, first seen Aug 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- gabrielkoerich/skills★ 8same name
- apideck-libraries/api-skills★ 4same name
- fore-vip/skills★ 1same name
- petr-korobeinikov/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- security-checkSkill
- environment-checkSkill
- run-verificationSkill
- refactorSkill
- debug-session-archivedSkill
- generate-guardsSkill
- check-anthropicSkill
- code-reviewerSkill
- code-reviewSkill
- debug-sessionSkill
- end-sessionSkill
- evolve-checkSkill
- evolveSkill
- fix-bugSkill
- forgetSkill
- frontend-designSkill
- guardSkill
- kit-healthSkill
- learnSkill
- map-codebaseSkill
- modeSkill
- parallel-prototypesSkill
- planSkill
- powershell-safeSkill
- product-riskSkill
- progress-reportSkill
- prototype-hypothesisSkill
- recallSkill
- refactoring-uiSkill
- scan-codebaseSkill
- scan-conventionsSkill
- search-firstSkill
- search-memorySkill
- shadow-codeSkill
- skill-creatorSkill
- smart-resumeSkill
- start-sessionSkill
- strategic-compactSkill
- tourSkill
- ux-heuristicsSkill
- verification-loopSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Read all three sources at once:
- Distinctive: line 77
If user says yes / go / do it:
- Distinctive: line 79
No re-asking, no re-summarizing
- Very specific: line 80
After completion, update [MEM]/todo.md (check off or add follow-up) and [MEM]/session_journal.md
- Distinctive: line 82
If user says skip:
- Distinctive: line 86
If user says "show me the full context":
- Distinctive: line 93
Never propose more than one action at a time — focus wins over completeness
- Very specific: line 94
If context is genuinely ambiguous (no journal entries, empty todo, silent STATUS.md), say so and ask what to work on — act cannot invent …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: act
Description
Reads the last session journal entries, open todos, and active plans to infer current intent — then proposes and executes the single most useful next action without being asked.
Trigger phrases:
- "act"
- "what should we do next"
- "pick up where we left off"
- "what were we doing"
- "continue"
- "resume"
- (also fires automatically at Start Session if there are open High-priority todos)
Steps
Step 1 — Read context (parallel)
Read all three sources at once:
[MEM]/session_journal.md— last 40 lines (recent session summaries)[MEM]/todo.md— full file (High/Medium priorities only)[MEM]/plans/— list open (non-archived) plan files, read the most recently modified one
Read([MEM]/session_journal.md, offset=last 40 lines)
Read([MEM]/todo.md)
Glob([MEM]/plans/*.md, excluding plans/archive/)Step 2 — Infer intent
From the context read, identify:
- What was being built/fixed — look for the last task mentioned in session_journal.md
- What's blocked or open — todos marked
[ ]with High priority - What plan is active — any plan file with
Status: In ProgressorStatus: Draft
Rank candidates:
- An in-progress plan with an identified next step
- A High-priority open todo
- The last thing mentioned in session_journal.md
Step 3 — Propose one specific action
State exactly what you propose to do. Be specific — not "continue the feature" but:
"Last session we finished the Java method for
adminSendIntroEmailbut hadn't wired the HFmtWebservice endpoint yet. I'll add the routing line and test it now."
Or:
"Your todo.md has one High-priority open item: 'Fix session tab scroll position reset on mobile'. I'll investigate the CSS/JS cause now."
Format:
## Picking up
**Last context:** [1 sentence from session_journal]
**Open item:** [specific todo or plan step]
**Proposed action:** [exactly what I'll do in the next 2 minutes]
Go? (yes / skip / show me the full context)Step 4 — Execute on confirmation
If user says yes / go / do it:
- Execute the proposed action immediately
- No re-asking, no re-summarizing
- After completion, update
[MEM]/todo.md(check off or add follow-up) and[MEM]/session_journal.md
If user says skip:
- Show the next candidate from the ranked list
- Repeat step 3
If user says "show me the full context":
- Print the relevant section from session_journal.md + the matched todo/plan
Notes
- Never propose more than one action at a time — focus wins over completeness
- If context is genuinely ambiguous (no journal entries, empty todo, silent STATUS.md), say so and ask what to work on —
actcannot invent intent from nothing; it surfaces what's already been decided - This skill is intentionally opinionated — it picks one thing and drives it
- Pairs with
search-memorywhen the proposed action needs prior-art research first - "act" on Clankbrain kit tasks = look at D:\claude-memory-starter changes
- "act" on webapps tasks = look at the TicTacWisdom/InfoGrasp codebase
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.

