subscope-pulse
/subscope-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", "/subscope-pulse", "obsidian pulse digest", "reddit engage weekly recap", "what did subscope surface this week".
- Author
- dancolta ↗
- Repository
- subscope ↗
- Licence
- MIT
- Last repository change
- 12.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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".
Triggers from the description
Original author 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".
How it works
- Preflight
- Generate digest
- Write to Obsidian
- After write
SKILL.md preview
---
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:
```bash
cat ~/.config/subscope/obsidian.yml 2>/dev/null
```
Expected shape:
```yaml
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
```bash
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.
Versions
The database has no other skills named subscope-pulse.
Database snapshot: 13.11.2026 · package version ece4a3fba00c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95subscope-run
Run the daily Reddit pain-post surface. Fetch new posts from configured subs, score by intent/keyword/freshness, optionally classify via Claude Haiku, dedup against history, hold in cooling queue, and emit inline markdown (plus optional Notion sync). Triggers on "run subscope",… - 95subscope-setup
Reconfigure individual pieces of subscope after first-run onboarding. Use this when you want to add or change LLM provider, swap a destination (Notion / Slack / Obsidian), or rotate credentials. NOT the first-run flow. First-time users should run /subscope-onboard instead.… - 91obsidian-tracker-pulse
Cross-project status overview and analytics. Use when the user invokes /pulse. - 100aa-kpi-pulse
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also… - 100cja-kpi-pulse
Produces a compact KPI digest showing how key metrics changed over a period and what's driving the movement. Use this skill when someone asks for a performance summary, a weekly recap, a morning briefing, a KPI update, or any variation of "how did we do this week/month." Also… - 100weekly-digest
Automated weekly summary of what changed in your product — top frustrations, new errors, trends up/down, conversion changes. Use when asking "what changed this week", "give me the weekly recap", or "what's new since last week.