/pulse
Weekly Obsidian digest of subscope activity. Builds a sub × surface heat map plus tier counts for the trailing 7 days, writes it as a dated markdown note to the user's Obsidian vault. Optional — skipped if Obsidian vault not configured. Triggers on "weekly pulse",
Claude Code
$ npx -y skills add dancolta/subscope --skill pulse --agent claude-code
Codex
$ npx skills add dancolta/subscope --skill pulse -a codex -y
Cursor
$ npx skills add dancolta/subscope --skill pulse -a cursor -y
Gemini CLI
$ npx skills add dancolta/subscope --skill pulse -a gemini-cli -y
GitHub Copilot
$ npx skills add dancolta/subscope --skill pulse -a github-copilot -y
OpenCode
$ npx skills add dancolta/subscope --skill pulse -a opencode -y
Windsurf
$ npx skills add dancolta/subscope --skill pulse -a windsurf -y
SKILL.md
pulse.SKILL.mdname: subscope-pulse
description: Weekly Obsidian digest of subscope activity. Builds a sub × surface heat map plus tier counts for the trailing 7 days, writes it as a dated markdown note to the user's Obsidian vault. Optional — skipped if Obsidian vault not configured. Triggers on "weekly pulse", "/subscope-pulse", "obsidian pulse digest", "reddit engage weekly recap", "what did subscope surface this week".
allowed-tools: Bash, Read, Write
/subscope-pulse
Weekly reflection layer. Notion is the daily-triage surface; Obsidian is the weekly-review surface where you spot patterns over time.
Preflight
Check for Obsidian vault config:
cat ~/.config/subscope/obsidian.yml 2>/dev/null
Expected shape:
vault_path: /Users/dan/Documents/MyVault
pulse_folder: subscope # optional, defaults to 'subscope'
If `obsidian.yml` missing: print "Obsidian vault not configured. Run `/subscope-onboard` to wire it (or drop `~/.config/subscope/obsidian.yml` with a `vault_path:` line manually), then re-run."
Generate digest
cd "$CLAUDE_PLUGIN_ROOT" && PYTHONPATH=engine python3 -c "
from subscope.lib import store, obsidian_sync
with store.connect() as conn:
print(obsidian_sync.build_weekly_digest(conn))
"That prints the markdown digest content to stdout.
Write to Obsidian
Use the **obsidian MCP** to write the digest:
1. Compute the filename: `YYYY-WNN-pulse.md` (current ISO week) 2. Compute the path: `<vault_path>/<pulse_folder>/<filename>` (create the folder if missing) 3. Call `mcp__obsidian__create-note` with that path and the markdown body from the previous step
If obsidian MCP not available (rare — Dan has it installed by default), fall back to writing the file via the host filesystem (`Bash: mkdir -p ... && cat > ...`).
After write
Print one line:
Pulse written: <vault_path>/<pulse_folder>/<filename> (N surfaces this week)
Do not print the digest body. Dan reads it in Obsidian.
Read more
name: subscope-pulse description: Weekly Obsidian digest of subscope activity. Builds a sub × surface heat map plus tier counts for the trailing 7 days, writes it as a dated markdown note to the user's Obsidian vault. Optional — skipped if Obsidian vault not configured. Triggers on "weekly pulse", "/subscope-pulse", "obsidian pulse digest", "reddit engage weekly recap", "what did subscope surface this week". allowed-tools: Bash, Read, Write
/subscope-pulse
Weekly reflection layer. Notion is the daily-triage surface; Obsidian is the weekly-review surface where you spot patterns over time.
Preflight
Check for Obsidian vault config:
cat ~/.config/subscope/obsidian.yml 2>/dev/null
Expected shape:
vault_path: /Users/dan/Documents/MyVault pulse_folder: subscope # optional, defaults to 'subscope'
If `obsidian.yml` missing: print "Obsidian vault not configured. Run `/subscope-onboard` to wire it (or drop `~/.config/subscope/obsidian.yml` with a `vault_path:` line manually), then re-run."
Generate digest
cd "$CLAUDE_PLUGIN_ROOT" && PYTHONPATH=engine python3 -c "
from subscope.lib import store, obsidian_sync
with store.connect() as conn:
print(obsidian_sync.build_weekly_digest(conn))
"That prints the markdown digest content to stdout.
Write to Obsidian
Use the **obsidian MCP** to write the digest:
1. Compute the filename: `YYYY-WNN-pulse.md` (current ISO week) 2. Compute the path: `<vault_path>/<pulse_folder>/<filename>` (create the folder if missing) 3. Call `mcp__obsidian__create-note` with that path and the markdown body from the previous step
If obsidian MCP not available (rare — Dan has it installed by default), fall back to writing the file via the host filesystem (`Bash: mkdir -p ... && cat > ...`).
After write
Print one line:
Pulse written: <vault_path>/<pulse_folder>/<filename> (N surfaces this week)
Do not print the digest body. Dan reads it in Obsidian.
subscope reads Reddit for you and hands you the threads worth replying to: the people shopping for what you sell, and the questions you can answer to build authority. Run it whenever you want.
More skills from other plugins.
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use…
seo
Comprehensive SEO analysis for any website or business type. Full site audits, single-page analysis, technical SEO (crawlability,…
brag
Turn the current project website into a short, polished, shareable launch video using Hyperframes. Use when someone says "/brag",…
geo-audit
Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit…
Questions about pulse.
- Which coding agents can use pulse?
- pulse installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

