session-to-post
Skill0 starsChanged 4 months agoMITView on GitHub
Turn a completed coding session, git diff, notes, or transcript into a development diary draft or end-of-session writeup without rewriting the story by hand. Use near the end of meaningful work when the user wants a durable wrap-up.
In this repository37 other files it gives its agents.
- adr-logSkill
- adversarial-reviewSkill
- ai-writing-detoxSkill
- autonomous-video-pipelineSkill
- browser-tutorial-videoSkill
- codex-execution-packSkill
- continuity-ledgerSkill
- github-mobile-opsSkill
- github-seoSkill
- idea-validationSkill
- illustration-promptSkill
- issue-control-loopSkill
- justdoitSkill
- lazy-seniorSkill
- long-context-dispatchSkill
- openclaw-councilSkill
- parallel-worktreesSkill
- playwrightSkill
- product-councilSkill
- product-shapingSkill
- public-artifact-laneSkill
- readme-generatorSkill
- screenshotSkill
- spec-bundleSkill
- spreadsheetSkill
- spreadsheet-tabular-analysisSkill
- spreadsheet-xlsx-editSkill
- tool-scoutSkill
- transcribe-basicSkill
- transcribe-diarizeSkill
- transcribeSkill
- triage-findingSkill
- video-builderSkill
- video-render-runSkill
- video-spec-builderSkill
- visual-explainerSkill
- work-shapingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
Do not use when: the work is still changing rapidly, the user only wants a mid-session checkpoint, or there is no real session evidence.
≈ “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
Session to Post
Metadata
- Trigger when: the session is winding down and there is real evidence such as a repo diff, saved patch, notes, or transcript.
- Do not use when: the work is still changing rapidly, the user only wants a mid-session checkpoint, or there is no real session evidence.
Skill Purpose
Convert real session artifacts into a grounded wrap-up or post draft so the work, lessons, and pivots survive the session in a reusable form.
Instructions
- Decide whether the user wants a full post draft or only a short wrap-up note. Do not overuse the full draft path when a compact internal summary would do.
- Choose the best source inputs and run the
session-to-postCLI with explicit paths. Read~/.codex/skills/session-to-post/README.mdfor the current flag set and source-selection rules if needed, especially when deciding between repo diff, saved patch, notes, and transcript inputs. - Review the generated result for groundedness, privacy, and signal. Keep the story anchored to decisions, failures, and pivots from the real session; if it is not public-safe, keep the output private-safe by default.
Non-Negotiable Acceptance Criteria
- The draft stays anchored to real session evidence.
- Public-safe framing is the default unless the user explicitly asks for private internal notes.
- The output does not become a file-by-file tour when the real story is about decisions or lessons.
- The skill does not auto-run just because a session ended; the user still has to want a write-up.
Output
- The draft text or saved draft path.
- The source artifacts used to build it.
- A note on whether the result is a public draft, a private note, or a short internal wrap-up.
Next skill options(only if needed):$public-artifact-lane— turn the session draft into a public-facing artifact;$ai-writing-detox— remove synthetic tone before sharing;$visual-explainer— add a supporting HTML explainer if the story needs diagrams or structure.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

