New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Ce Product Pulse

by EveryInc in EveryInc/compound-engineering-plugin

Generate time-windowed product pulse reports from configured signals.

MITAuto-check: notes

Install Ce Product Pulse

skills CLI
$ npx skills add EveryInc/compound-engineering-plugin --skill ce-product-pulse -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install EveryInc/compound-engineering-plugin ce-product-pulse --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/EveryInc/compound-engineering-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/ce-product-pulse .claude/skills/ce-product-pulse && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ce-product-pulse
GitHub stars
25k
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
1,104 words
Files
7 (incl. references)
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

Generate time-windowed product pulse reports from configured signals.

  • Works in 4 steps: Route by config state → First-run interview → Run the pulse → …
  • SKILL.md covers Boundaries, Interaction Method, Lookback Window and Artifact Root, plus 4 more sections
  • Calls git

What it does

Ce Product Pulse is an agent skill from EveryInc/compound-engineering-plugin. Generate time-windowed product pulse reports from configured signals.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `agents/openai.yaml`, `references/config.md` and `references/interview.md`).

The repository describes itself as: Official Compound Engineering plugin for Claude Code, Codex, Cursor, and more. The licence is MIT.

Example prompts

  • “/ce-product-pulse”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Glob, Grep, Bash, AskUserQuestion

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Route by config state
  2. First-run interview
  3. Run the pulse
  4. Scheduling

What it can do on your machine

Read from SKILL.md and the folder at commit 67035e9. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Glob
    • Grep
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Ce Product Pulse loads about 1.9k tokens when it runs, and up to ~11k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 1,104 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~11k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Glob, Grep, Bash, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from EveryInc/compound-engineering-plugin at commit 67035e9, republished under its MIT licence (© EveryInc). 1,104 words, ~1,942 tokens.

Download SKILL.mdSave it as .claude/skills/ce-product-pulse/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
ce-product-pulse
description
Generate time-windowed product pulse reports from configured signals.
allowed-tools
Read, Write, Glob, Grep, Bash, AskUserQuestion
disable-model-invocation
true
argument-hint
[lookback window, e.g. '24h', '7d', '1h'; default 24h]

Product Pulse

ce-product-pulse queries the product's data sources for a given time window and produces a compact, single-page report covering usage, performance, errors, and followups. The report is saved to <root>/pulse-reports/ and the key points are shown in chat.

Done: a report of 30-40 lines exists at <root>/pulse-reports/YYYY-MM-DD_HH-MM.md, its headlines and top followup are in chat, and Phase 3 (Scheduling) has been reached.

Boundaries

  • Read-only, everywhere. The skill does not mutate the product, the database, or any external system. Its only writes are pulse settings appended to .compound-engineering/config.local.yaml (interview and opt-out writes stay on the local override) and the report file. MCP and other data-source tools are invoked read-only; if a tool offers write modes, do not use them. A database source must be a read-only connection — the interview refuses read-write credentials, and DB access is optional, since many products complete the pulse with analytics and tracing alone.
  • No PII in saved reports. No user emails, account IDs, or message content in the file written to disk.
  • Read it like a founder. No hardcoded thresholds, no default "good"/"bad" labels, no alerting: present the numbers and let the reader judge.
  • Single page. Target 30-40 lines. If a section is thin, leave it thin; if the report is getting long, cut.
  • Not a shipping log or a dashboard replacement. Shipped work lives in the issue tracker and commit history. Deep investigation still uses the native tools; this consolidates a single-page read, and every run is saved so past pulses browse as a timeline.

Interaction Method

Default to the host's blocking question tool already in the current tool list (match by capability, not by a host-specific name). Presence in the current tool list is proof the tool exists; never call a user-facing question tool to discover whether it exists. If a matching tool is listed but unloaded, use the host's tool-discovery primitive to load that capability — do not search for another host's tool name. Fall back to numbered options on the host's user-visible chat surface only when no such tool is in the list or a real question call errors. Never silently skip the question.

Ask one question at a time. Reserve multi-select for first-run configuration only.

Lookback Window

The lookback window is the time range this skill was invoked with (e.g. 24h, 7d) — present in the current prompt or conversation, whether the user gave it directly or a calling skill passed it. Common forms are trailing hours (24h, 48h, 72h), trailing days (7d, 30d), and 1h for launches.

If the argument is empty, default to pulse_lookback_default from config (resolved in Phase 0, Route by config state); if that is also unset, fall through to the hard default of 24h. If the argument is unparseable, ask the user to clarify.

Apply a 15-minute trailing buffer to the window's upper bound. Many analytics and tracing tools have ingestion lag; querying right up to now under-reports the most recent events. For a 24h window, query [now - 24h - 15m, now - 15m].

Artifact Root

This skill writes pulse reports under <root>/pulse-reports/. Resolve <root> when you first compose a <root>/ path (per the block below), never before you need it. A write to <root>/... and a read of <root>/solutions/ both count as composing a <root>/ path, so either one triggers resolution; only a run that touches no <root>/ path at all -- a scratch-only or no-repo flow -- skips it.

<!-- ce-docs-root:start -->

Resolve the CE artifact root <root> before composing any artifact path.

  • Read docs_root from <repo-root>/.compound-engineering/config.yaml only (<repo-root> = git rev-parse --show-toplevel). Do not read it from config.local.yaml. Unset -> <root> is docs, exactly as before.
  • Validate a set value: a repo-relative directory whose real, symlink-resolved path stays inside the repo and is neither the repo root nor under .git/. Otherwise stop with an error naming docs_root and the value -- never fall back to docs.
  • Use <root> as the sole artifact location: create it if absent, compose each path as <root>/<subdir> with this skill's own subdirectory, and never also read docs.
<!-- ce-docs-root:end -->
Show full SKILL.md (448 more words)Show less

Phase 0: Route by config state

<!-- ce-config-layers:start -->

Resolve ordinary CE yaml keys from the two repo files.

  • Read <repo-root>/.compound-engineering/config.local.yaml, then config.yaml (<repo-root> = git rev-parse --show-toplevel). Missing files are skipped. Gitignore does not change resolution.
  • Win with the first active (non-commented) value. For scalars, empty is unset; an invalid value continues to the next layer, then the skill default. For lists and maps, a present key — including an empty list or map — replaces the whole key.
  • Do not use this rule for docs_root — that key is config.yaml only.
<!-- ce-config-layers:end -->

Resolve <repo-root> with git rev-parse --show-toplevel, then apply the ordinary-key rule above to the pulse_* keys. Read references/config.md whenever a pulse_* value has to be interpreted — it is the key schema and nothing else: each key, its allowed values, and its default, with an unset or invalid value taking the documented default rather than being guessed.

Routing: every run passes through Phase 2 (Run the pulse) and then Phase 3 (Scheduling). Run Phase 1 (First-run interview) first when pulse_product_name is unset after cascade (the ordinary-key rule above), when the repo root cannot be resolved, or when the argument was setup, reconfigure, or edit config. Otherwise start at Phase 2 (Run the pulse).

Phase 1: First-run interview

Read references/setup.md first; this read is required. It defines the strategy-doc seeding, the interview order and its pushback bar, the read-write database refusal, how the config is written to config.local.yaml without disturbing other keys, and the one-time scheduling offer. The questions themselves come from references/interview.md, which that file names as its own required read.

Phase 2: Run the pulse

If Phase 1 (First-run interview) ran, re-apply the ordinary-key rule (local then tracked) from the repo root using the native file-read tool before any query, to pick up edits accepted during the Phase 1 review step. Otherwise use the pulse_* values already extracted in Phase 0 (Route by config state), applying the defaults in references/config.md for anything unset.

Then read references/run.md before dispatching any query; this read is required. It defines which queries run in parallel and which run serially, the pulse_db_enabled check that decides whether database work runs, the optional quality sampling and its scoring discipline, the four report sections, and where the report is written.

Phase 3: Scheduling

Setup offers a recurring run once (references/setup.md). On later runs, mention it again lightly: if the argument was a schedule keyword (daily, hourly, weekly), say this run is ad-hoc and point at the harness's scheduling primitive; if no schedule is on file and this is the third or later run, mention once that scheduling is available. Do not nag on every run, and never schedule automatically — any handoff to a scheduling primitive requires explicit confirmation.

© EveryInc, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in skills/ce-product-pulse of EveryInc/compound-engineering-plugin.

  • SKILL.md
  • agents/openai.yaml
  • references/config.md
  • references/interview.md
  • references/report-template.md
  • references/run.md
  • references/setup.md

Open the folder on GitHubat commit 67035e9

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in EveryInc/compound-engineering-plugin, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Ce Product Pulse next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Ce Product Pulse compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Ce Product Pulse this skillEveryInc/compound-engineering-plugin25k1 repos~1.9kAutomated safety check: NotesMIT
Configuring Windows Event Logging For Detectionmukul975/Anthropic-Cybersecurity-Skills34k—~1.6kAutomated safety check: PassApache-2.0
Pulsealirezarezvani/claude-skills28k—~3.8kAutomated safety check: PassMIT
Configuring Windows Defender Advanced Settingsmukul975/Anthropic-Cybersecurity-Skills34k—~3.1kAutomated safety check: PassApache-2.0
Configure Channelopenclaw/openclaw392k—~946Automated safety check: PassMIT
Windows Desktop E2Eaffaan-m/ECC276k1 repos~7.6kAutomated safety check: PassMIT

Similar skills

  • Configuring Windows Event Logging For Detection

    mukul975/Anthropic-Cybersecurity-Skills

    Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation.

    34k GitHub stars~1.6k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Pulse

    alirezarezvani/claude-skills

    Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days).

    28k GitHub stars~3.8k tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Configuring Windows Defender Advanced Settings

    mukul975/Anthropic-Cybersecurity-Skills

    Configures Microsoft Defender for Endpoint (MDE) advanced protection settings including attack surface reduction rules, controlled folder access, network protection, and exploit protection.

    34k GitHub stars~3.1k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Configure Channel

    openclaw/openclaw

    Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.

    392k GitHub stars~946 tokensUpdated today
    Auto-check passed

  • Windows Desktop E2E

    affaan-m/ECC

    E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation.

    276k GitHub starsUsed in 1 repo~7.6k tokens
    Testing & QAAuto-check passed

  • Windows Desktop E2E

    affaan-m/ECC

    E2E testing for Windows native desktop apps (WPF, WinForms, Win32/MFC, Qt) using pywinauto and Windows UI Automation.

    276k GitHub stars~5.5k tokensUpdated today
    Testing & QAAuto-check passed

More from EveryInc/compound-engineering-plugin

All 37 skills in this repo

  • Compound Learning Writer

    EveryInc/compound-engineering-plugin

    Records one solved and verified problem as a durable learning in the repository, but only when the reasoning is not already clear from the final code, tests or docs.

    25k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Compound Learnings Refresh

    EveryInc/compound-engineering-plugin

    Audits a repo's stored learnings against the current codebase, fixes stale, overlapping or superseded docs and reports on every document.

    25k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • Compound Engineering Prototype

    EveryInc/compound-engineering-plugin

    Builds a throwaway prototype at just the fidelity needed to settle a specific how-it-should-work-or-feel question, before committing to an approach other work will treat as fixed.

    25k GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

  • Compound Engineering Setup

    EveryInc/compound-engineering-plugin

    Checks Compound Engineering plugin health and repo-local config, or scaffolds a Compound Pack when you ask for one by id.

    25k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • PR Babysitter

    EveryInc/compound-engineering-plugin

    Watches an open GitHub pull request over time, routing review comments and CI failures to other skills until the PR is ready to merge.

    25k GitHub stars~2k tokensUpdated 2 days ago
    Auto-check passed

  • CE Brainstorm

    EveryInc/compound-engineering-plugin

    Turns a vague or ambitious feature idea into a requirements-only plan through dialogue with you, sized to the work, before any code is written.

    25k GitHub stars~1.9k tokensUpdated 2 days ago
    Auto-check passed

Questions about Ce Product Pulse

What does Ce Product Pulse do?

Generate time-windowed product pulse reports from configured signals. Ce Product Pulse is an agent skill from EveryInc/compound-engineering-plugin. Generate time-windowed product pulse reports from configured signals.

How do I install Ce Product Pulse in Claude Code?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-product-pulse -a claude-code`. Or copy the skill folder (skills/ce-product-pulse in EveryInc/compound-engineering-plugin) into .claude/skills/ce-product-pulse in your project. Claude Code loads it when a task matches its description.

How do I install Ce Product Pulse in Codex?

Run `npx skills add EveryInc/compound-engineering-plugin --skill ce-product-pulse -a codex`. Or copy the skill folder (skills/ce-product-pulse in EveryInc/compound-engineering-plugin) into .agents/skills/ce-product-pulse in your project. Codex loads it when a task matches its description.

Can I use Ce Product Pulse in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add EveryInc/compound-engineering-plugin --skill ce-product-pulse -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ce-product-pulse, .gemini/skills/ce-product-pulse, .github/skills/ce-product-pulse and .opencode/skills/ce-product-pulse in your project.

What does Ce Product Pulse need to run?

Going by SKILL.md and its folder, Ce Product Pulse needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Read, Write, Glob, Grep, Bash, AskUserQuestion.

Does Ce Product Pulse access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Ce Product Pulse safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Ce Product Pulse use?

Ce Product Pulse is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Ce Product Pulse use?

About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9k tokens, read only when the agent opens those files.

What are the alternatives to Ce Product Pulse?

Skills that share tags, products or a category with Ce Product Pulse: Configuring Windows Event Logging For Detection (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Pulse (alirezarezvani/claude-skills, 28k stars), Configuring Windows Defender Advanced Settings (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Configure Channel (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Ce Product Pulse?

EveryInc (a GitHub organization) maintains it in EveryInc/compound-engineering-plugin, which has 25,447 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 8, 2026.

Source: EveryInc/compound-engineering-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.