Automated summary
Runs the quarter-boundary ritual: rolls quarter-scoped project folders, archives finished projects, grades the closing quarter's goals and OKRs, and drafts the next quarter's goals behind an approval gate.
Strengths
- The `python3 tools/quarter_path.py --check` drift check doubles as a todo list and gives a clean no-op exit when there is nothing to do.
- Enforces grading the closing quarter before rewriting goals, and hard-blocks writing new goals until the user approves them.
- Grades from checkable evidence (shipped files, closed task rows, daily notes, financial numbers) instead of impressions, and flags missing evidence rather than guessing.
- Archive-never-delete via `git mv`, with relative-link depth fixes and explicit exceptions for living documents, daily notes, and areas.
Limitations
- Assumes an existing workspace layout (projects/, areas/, daily/, archive/, tools/quarter_path.py) plus the referenced `workflows/quarter_rollover.md` SOP, so it is not portable as-is.
- Requires git and Python 3, and defers most of the procedure to the SOP, which must be read before acting.
- The approval gate and evidence requirements mean it cannot fully automate goal-setting; it needs founder input.
Use it at a quarter boundary, or when back-filling a late close, to shut one quarter and open the next across the whole workspace.
Don't use it for daily task triage (/triage-tasks) or a repository health check (/audit), or when the quarter_path tooling is missing from the repo.
Security analysis
CautionThe skill is not overtly malicious and explicitly avoids deletion or exfiltration, but it grants powerful local Bash/Edit/Write capabilities and relies on an external SOP that is not shown. That makes its effective behavior only partially auditable, so it warrants caution rather than safe.
- •Declares Bash/Write/Edit and instructs running local Python plus git mv, enabling broad workspace file moves and edits.
- •Delegates execution to an external authoritative workflows/quarter_rollover.md that is not included in SKILL.md, so the full instruction surface cannot be audited from the skill file alone.
- •Archiving/moving project folders and editing README/GOALS files may occur without per-action confirmation; only the new-quarter GOALS write has an explicit approval gate.
- •No network calls, secret access, obfuscated payloads, destructive deletion, or curl|sh patterns observed; archive uses git mv rather than delete.
Examples
/quarter-rollover — close out Q2 and set up Q3.Roll the quarter: run quarter_path.py --check, grade last quarter's OKRs against evidence, then show me draft goals for the new quarter before writing anything.tools/quarter_path.py --check reports drift — do the quarter rollover and archive the finished projects.name: quarter-rollover description: Run the quarter-boundary ritual — roll the quarter-scoped project folders, archive finished projects, grade the closing quarter's GOALS/OKRs, and draft the new quarter's goals behind an approval gate. Trigger on /quarter-rollover, "quarter rollover", "roll the quarter", "close out Q2", "new quarter setup", or when tools/quarter_path.py --check reports drift. Distinct from /triage-tasks (daily gate) and /audit (repo health check). allowed-tools:
- Bash
- Read
- Edit
- Write
- Glob
- Grep model: opus
Quarter Rollover — skill entry point
You are running the quarter-rollover skill. It executes the SOP at
workflows/quarter_rollover.md, which is
authoritative — read it first and follow its seven steps. Do not duplicate its
content here; consume it.
What this skill does
Closes one calendar quarter and opens the next across the whole workspace: project folders roll and go cold, finished work is archived, the closing quarter's goals and OKRs are graded against evidence, and the new quarter's goals are drafted for approval.
Start with python3 tools/quarter_path.py --check — its output is your todo
list. If it exits 0 and projects/ has no dormant folders, say so and stop;
there is nothing to invent.
Load-bearing rules (do not improvise)
- Grade before you rewrite. Step 4 (grade the closing quarter) comes before Step 5 (write the new one). A quarter overwritten un-graded destroys the track record and quietly ratchets down ambition. If the user pushes to skip straight to new goals, say plainly what gets lost, then follow their call.
- Step 5 is a hard approval gate. Draft the new quarter's goals from evidence
and present them in chat. Do NOT write them into
areas/personal/GOALS.mduntil the user approves or edits. Grading is evidence work you own; deciding what the next 90 days are for is a founder taste call you don't. - Grade from evidence, not vibes. Every verdict cites something checkable —
a shipped file, a
Closedtask row, adaily/note, a financial number. Docs drift optimistic and under-credit shipped work; check both directions and say when evidence is missing rather than guessing a grade. - Never hard-code a quarter path. Pipelines resolve their folder via
python3 tools/quarter_path.py <slug>. If you find a literalprojects/YYYY-QN-…in a workflow, skill, or agent file, that's a regression — fix it and mention it. - Archive, never delete. Closed project folders move to
archive/YYYY/withgit mv. Fix relative-link depth after the move (one level deeper) and leave a closing pointer to the successor folder in the archived README. - Respect the exceptions. Living-document projects (files updated in place, not one-dated-file-per-run) do not roll even if their folder carries a legacy quarter prefix; daily notes never archive; areas never roll. See the SOP's Exceptions section before "fixing" any of them.
Arguments
Optional $ARGUMENTS: a quarter to close (e.g. 2026-Q2) when running late or
back-filling. Default: close the quarter that just ended relative to today.
Start now
Read workflows/quarter_rollover.md,
run python3 tools/quarter_path.py --check, and begin at Step 1.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/quarter-rollover-msh3us6d/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/quarter-rollover-msh3us6d' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/quarter-rollover-msh3us6d/download' --output '.skill-downloads/quarter-rollover-msh3us6d/SKILL.md.part' && mv '.skill-downloads/quarter-rollover-msh3us6d/SKILL.md.part' '.skill-downloads/quarter-rollover-msh3us6d/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/quarter-rollover-msh3us6d/SKILL.md' && test -s '.skill-downloads/quarter-rollover-msh3us6d/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/quarter-rollover' && cp -R '.skill-downloads/quarter-rollover-msh3us6d' '.claude/skills/quarter-rollover'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/quarter-rollover-msh3us6d'openskills read 'quarter-rollover-msh3us6d'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/quarter-rollover-msh3us6d/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
PDF Reader
Productivity
Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.
Discord Messaging Workflows
Productivity
Use the message tool to send, edit, and moderate Discord messages with interactive components.
Interactive Verdict Preview
Productivity
Generate an interactive HTML preview of keep/drop verdicts for maintainer review, then process the pasted feedback JSON.