petekp/session-scope-guard
skills/claude-code-audit-workspace/iteration-1/eval-2-casual-phrasing/with_skill/outputs/audit/drafts/skills/session-scope-guard/SKILL.md
Enforces one-subtask-per-session discipline for long Claude Code workflows. Use at the start of any prompt that begins a new subtask, or when the current session has already exceeded 60 tool uses or 45 minutes. Proposes a handoff + new session instead of continuing to pile work into the current thread. Especially valuable for users running Circuit or Codex workflows who tend to accumulate 100+ tool uses per session and then pay heavy re-entry cost on the next resume.
$ install --global
skillsauthnpx skillsauth add petekp/claude-skills session-scope-guardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 1, 2026, 1:55 AM140.7s1 file scanned
SKILL.md
- name:
- session-scope-guard
- description:
- Enforces one-subtask-per-session discipline for long Claude Code workflows. Use at the start of any prompt that begins a new subtask, or when the current session has already exceeded 60 tool uses or 45 minutes. Proposes a handoff + new session instead of continuing to pile work into the current thread. Especially valuable for users running Circuit or Codex workflows who tend to accumulate 100+ tool uses per session and then pay heavy re-entry cost on the next resume.
Session scope guard
Why this exists
In the audited workspace, 16 of 25 sampled sessions began with a bare resume or resume handoff. The average session ran 145 tool uses and 452 minutes. Two sessions ended with the user explicitly saying they had lost track of what the session was doing.
The pattern underneath: a session that "stays open" keeps being used for whatever the user asks next, even when the next ask is a new subtask. Claude happily continues. The cost is paid later, when the session either overruns context, the user forgets the state, or the next resume has to rebuild it all.
The fix is a decision checkpoint at the moment the user introduces a new subtask.
When this fires
- The user's prompt introduces a new subtask distinct from the one the current session started on.
- AND one of these is true:
- The current session has >= 60 tool uses already.
- The current session has >= 45 minutes of wall-clock duration.
- The current session's topic has already shifted once.
"New subtask" test: if you would summarize the conversation up to this point and the user's new prompt under a single title, it is not a new subtask. If you'd need two titles, it is.
What to do
- Do not start executing the new subtask.
- Reply with a short message in this shape:
This looks like a new subtask. Current session has <N> tool uses / <M> min on <original topic>. Recommend: I save continuity now (circuit:handoff save) and you start the next chunk in a fresh session. Say "continue here" to override and stay in this session. - If the user says "continue here" or similar, drop the guard for the rest of the session — do not re-fire.
- Otherwise invoke
circuit:handoff savewith a goal describing the upcoming subtask, then stop. Do not begin the new subtask in the current session.
When NOT to fire
- The user's new prompt is clarification, correction, or a micro-follow-up on the existing subtask.
- The session is young (< 60 tool uses AND < 45 min).
- The user has explicitly asked for an extended autonomy run ("continue autonomously overnight", etc.) — that is a deliberate multi-hour session and this skill gets out of the way.
- The user just said "continue here" for this session already.
What a correct firing looks like
Bad (pre-fix):
User: resume handoff Claude: [executes 120 tool uses on subtask A] User: ok now can we also look at the paddock performance issue? Claude: [continues in same session, adds 60 more tool uses] User (later): I've totally forgotten what we're doing.
Good (with this skill):
User: ok now can we also look at the paddock performance issue? Claude: This looks like a new subtask. Current session has 120 tool uses / 64 min on "ADR-005 transcript consumer migration." Recommend: I save continuity now and you start the next chunk in a fresh session. Say "continue here" to override.
Related Skills
petekp/pr-self-review
development
VerifiedTrustedCommunity
Draft short, plainspoken notes in the author's voice that help reviewers understand non-obvious choices, boundaries, and preserved behavior in the author's own pull request or local diff. Use when the user asks to self-review, annotate, or add reviewer context to their PR or changes. Draft locally when no PR exists, and post approved notes as one GitHub review when a PR does exist. Do not use for reviewing someone else's PR, writing code comments, explaining code generally, or drafting a PR description. Never post without explicit approval.
40SKILL.mdUpdated Jul 21, 2026
petekp/tailwind-plugin-craft
tools
VerifiedTrustedCommunity
Design and build pure-CSS (zero-JavaScript) Tailwind CSS v4 plugins of unusual depth and craft. Use when the user wants to create, architect, or refine a Tailwind utility plugin or CSS effect — e.g. "make a tailwind plugin", "build a tw-* plugin", "a CSS-only shimmer/fade/glow/grain/noise utility", "tailwind v4 @utility", "package this effect as a plugin", or wants an effect with surprising visual depth (gradients, masks, filters, SVG filter tricks, scroll-driven animation). Pairs deep CSS/SVG technique research with a bespoke tuning workbench for dialing the effect in. Inspired by tw-fade and tw-shimmer.
40SKILL.mdUpdated Jul 15, 2026
petekp/pr-screenshot-comparison
content-media
VerifiedTrustedCommunity
Create clear, polished before-and-after screenshots for a GitHub pull request. Use when a UI change needs visual proof: capture matching states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
40SKILL.mdUpdated Jul 15, 2026
petekp/skills/latent-potential
testing
VerifiedTrustedCommunity
--- name: latent-potential description: First-principles, team-of-experts assessment of a software project that surfaces latent potential; underexploited assets, a sharper north star, missing high-leverage capabilities, better framing and messaging. Produces a prioritized, evidence-grounded report with cheap probes, a reframe candidate, a stop-doing list, and an honest skeptic's case. Use whenever the user wants fresh eyes on a project they have built: "what am I sitting on", "what could this be
40SKILL.mdUpdated Jul 15, 2026