pulse
Skill8 starsChanged 9 days agoMITView on GitHub
Read eight offline session signals and record the observation through the canonical seed writer.
21 other projects use a version of this.
Adopted by
Most recently taken up by
- hemal08ce094/DesignSkillsSwiftUItheir own version, first seen Nov 8, 2026
- lsnackerman/raw-clauding-skillstheir own version, first seen Nov 1, 2026
- pendo-io/Product-Looptheir own version, first seen Nov 1, 2026
- duthaho/skillhubtheir own version, first seen Oct 31, 2026
- bekhruztbx/ai-creative-teamtheir own version, first seen Oct 25, 2026
- simota/agent-skillstheir own version, first seen Oct 23, 2026
Used with
Projects with it also use ant, artistic and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
bergsideSkillant
Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.
Also in 3 projects that use this
bergsideSkillartistic
High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.
Also in 3 projects that use this
- +10 more from bergside
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 21
- bergside/awesome-design-skills★ 2.9ksame name
- Nunchi-trade/agent-cli★ 521same name
- simota/agent-skills★ 96same name
- lsnackerman/raw-clauding-skills★ 45same name
- bekhruztbx/ai-creative-team★ 18same name
- Hassaan146/claude-skills★ 18same name
- duthaho/skillhub★ 9same name
- linggen/skills★ 3same name
- wheslleyrimar/BuildCLI-Agents★ 3same name
- FeedbackPulseApp/hr-skills★ 2same name
11 more not listed
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 repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commandsSkill
- agentic-auditSkill
- agent-reviewSkill
- autonomous-dev-flowSkill
- batch-mergeSkill
- bug-huntSkill
- catchupSkill
- check-prSkill
- commitSkill
- create-issueSkill
- create-prSkill
- decideSkill
- decompose-issueSkill
- fix-ciSkill
- full-reviewSkill
- hallucination-checkSkill
- learnSkill
- manual-testing-modeSkill
- mergeSkill
- parallel-devSkill
- prime-directiveSkill
- project-auditSkill
- qa-updateSkill
- reconSkill
- session-lifecycleSkill
- skillSkill
- smoke-formSkill
- smoke-testSkill
- start-workingSkill
- swarm-auditSkill
- tackle-issuesSkill
- tiered-delegationSkill
- visual-briefSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
2
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
- Very specific: line 7
Read eight offline session signals and record the observation through the canonical seed writer.
- Distinctive: line 24
Observe into a scratch snapshot: Run the installed script, adding only appropriate arguments above.
- Distinctive: line 36
Persist only with the real session identity: When the host supplies the actual session ID, record the snapshot using the writer:
- Very specific: line 69
All subprocesses share a 0.8-second deadline.
“Common” is measured: kept by at least 6 in 10 of the 18 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
/pulse
Read eight offline session signals and record the observation through the canonical seed
writer. Use when the user requests /pulse, a quick session health check, or a boundary
readout. The underlying stdlib script calls no model, network service or test suite.
Arguments
$ARGUMENTS— optional--boundary,--topic,--sourceor--signals-fileoptions forsession-pulse.py. Pass--topiconly for a fleet topic, consistently to reader and writer.--sourcenames the actual host:claude,codexorchroxy. Leave it unspecified when unknown. Never consult Claude's meter for Codex/chroxy; the Claude arm additionally requires the real$CLAUDE_CODE_SESSION_ID.
Instructions
- Read, do not manufacture measurements. The script reads the canonical seed and local
git state. Tests and CI are cached STATE values, never fresh runs. Unknown measurements
are
n/a, including open counts and turns when no explicit cached count exists. Observe into a scratch snapshot. Run the installed script, adding only appropriate arguments above. Show its eight lines verbatim:
PULSE_SNAPSHOT=$(mktemp "${TMPDIR:-/tmp}/session-pulse.XXXXXX") python3 ~/.claude/scripts/session-pulse.py --snapshot-file "$PULSE_SNAPSHOT"Plain invocation is observational.
--snapshot-filemay write a scratch JSON file; it refuses seed names, aliases and the handoff directory. It does not write a seed. The reader always exits zero, including source, timeout and snapshot-output failures, so inspect the eight lines rather than treating the exit code as proof of persistence.Persist only with the real session identity. When the host supplies the actual session ID, record the snapshot using the writer:
python3 ~/.claude/scripts/session-seed.py write \ --refresh-pulse "$PULSE_SNAPSHOT" --session "$ACTUAL_SESSION_ID"ACTUAL_SESSION_IDis supplied by the host, never guessed from a worktree, a seed or the newest transcript. A real Claude host may omit--sessionand use its harness-provided environment ID. If the ID is unavailable, keep this pulse observational and report that it was not saved. Pass the reader's same--topicwhen applicable. Do not hand-edit the seed, even for a snapshot. The writer preserves the existing date/body/decisions, archives an incumbent owned by a different session and runs fresh canonical proof. Missing or hollow legacy seeds remain unchanged when refresh refuses. Report REFUSE or snapshot-save failure honestly; never claim the baseline was stored withoutseed:.- Act on the readout. A WARN never stops authorized work. Invoke
/decidefor an actual pending choice, respecting owner-reserved authority. Run/visual-briefwhen a pulse delta crosses a WARN threshold or at package close. End the surrounding response with the fleet four-slot**Status:**block and one-task**Next:**sentence.
Cached signals contract
--signals-file accepts only an explicitly supplied JSON object with source matching
--source and a full UTC observed_at. Optional open_items, turns and compactions are
nonnegative integers, never booleans. context_pct is a finite number from 0 to 100.
estimate and actual are finite nonnegative numbers supplied together with their common
nonempty unit. Keep their source and timestamp in the cached input; missing data stays
unknown. Do not estimate usage or context from spend, elapsed time or another host.
The eight lines cover scope; seed age and dispatch; HEAD/branch/tree/ahead/behind; commits
since seed/open items/turns; cached tests and CI; decisions count/age/default; usage/context/
compactions; and delta/WARN. Claude usage may come only from usage-pace.py --oneline.
All subprocesses share a 0.8-second deadline; unavailable sources degrade to n/a.
The readable Claude usage line remains the helper's bounded raw --oneline output.
Material comparison uses only supported printed measurements at that formatter's
precision: direct sd, fh and fable percentages; total or explicitly labelled subtotal
spend; fable spend; and derived capacity percentage/cap. Sample timestamps and ages,
reset countdowns, rates, burn, headroom and projected landings are excluded. Missing or
unrecognized measurements remain unknown. This small presentation signature reuses the
single bounded --oneline call; it neither recalculates accounting nor makes another
source call for a separate JSON report.
A missing previous snapshot says no baseline; unchanged material state says
no material change since TIME. Changed material fields are named. Decision recurrence
counts advance only when snapshots are persisted. Raw ages and recurrence counters do not
manufacture material changes, but stable threshold booleans make a newly crossed WARN
visible in delta and remain unchanged while the threshold remains crossed. WARN thresholds
are a repeated decision text across at least two recorded pulses,
more than three open items, a seed older than 24 hours, at least two compactions, a dirty
working tree at a boundary, or stated estimate drift above 25 percent. Legacy pending
DECISION prose warns with known age and unknown count until structured metadata is supplied.
Seed metadata contract
The full writer accepts --decisions-file containing a JSON list of
{"text":"Approve the proposed plan","opened_at":"2026-10-28T13:00:00Z","default":"Hold the proposed plan pending an answer"}
objects; default omission is an empty list. Carry every unresolved choice and its original
opened_at. This default is a recommended plan, never reserved execution authority.
--pulse-file carries a snapshot in a full seed write. --refresh-pulse updates snapshot and
session metadata only, preserving date and body. Both flow through the same validation,
archive and proof path. decisions and last_pulse are single-line JSON flow values within
YAML frontmatter; conventional block-style YAML is outside this stdlib contract.
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.

