mjmorales/notify-setup
skills/notify-setup/SKILL.md
Configure orchestrator notification reporters (Slack, Discord, MCP, custom). Generates bash scripts and updates .claude/.prove.json. Triggers on "notify setup", "set up notifications", "configure alerts".
$ install --global
skillsauthnpx skillsauth add mjmorales/claude-prove notify-setupInstall 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: Apr 16, 2026, 5:59 AM3.6s3 files scanned
SKILL.md
- name:
- notify-setup
- description:
- >
Notify Setup
Follow references/interaction-patterns.md for all AskUserQuestion usage.
Phase 1: Discovery
Scan existing integrations before prompting the user:
- Read
.claude/settings.jsonand~/.claude/settings.jsonfor MCP servers with messaging capabilities - Check environment for
SLACK_WEBHOOK_URL,DISCORD_WEBHOOK_URL - Check
.claude/.prove.jsonfor existing reporters - Report findings. If an existing reporter suffices, confirm before proceeding.
Phase 2: Platform Selection
AskUserQuestion, header "Platform". Annotate options with discovery results (e.g., "Slack (Webhook) -- SLACK_WEBHOOK_URL detected"):
- "Slack (Webhook)" -- posts via
SLACK_WEBHOOK_URLand curl - "Discord (Webhook)" -- posts via
DISCORD_WEBHOOK_URLand curl - "MCP Integration" -- reuses a detected MCP server's messaging tool
- "Custom Command" -- user-provided notification command
Phase 3: Configuration
Scope -- AskUserQuestion, header "Scope":
- "Project" -- scripts in
./.prove/, config in.claude/.prove.json - "Global" -- scripts in
~/.claude/scripts/
Events -- AskUserQuestion, header "Events" (multiSelect: true). Offer all reporter event types from references/validation-config.md: step-complete, step-halted, wave-complete, execution-complete, review-approved, review-rejected, validation-pass, validation-fail.
Platform-specific details (free-form):
- Slack: Webhook URL env var name (default
SLACK_WEBHOOK_URL), channel override, mention preferences - Discord: Webhook URL env var name (default
DISCORD_WEBHOOK_URL), mention role - MCP: Which MCP server and tool, channel/recipient
- Custom: Command to run, any env vars it needs
Phase 4: Script Generation
Generate a bash script tailored to the user's platform and preferences.
Requirements:
#!/usr/bin/env bash, POSIX-compatible- Read reporter env vars (
PROVE_EVENT,PROVE_TASK,PROVE_STEP,PROVE_STATUS,PROVE_BRANCH,PROVE_DETAIL) perreferences/reporter-protocol.md - Format a human-readable message from those vars
- Support
--testflag with dummy data - Fail gracefully -- use
|| trueand trap so the orchestrator is never blocked - Reference env vars for secrets; embed no URLs or tokens in the script
See references/platforms.md for platform-specific payload formats, curl patterns, and MCP invocation.
Write to ./.prove/notify-<platform>.sh (project) or ~/.claude/scripts/notify-<platform>.sh (global), then chmod +x.
Phase 5: Config Update
- Read
.claude/.prove.json(create if missing) - Add/update a
reportersentry, preserving all other config:{ "name": "<platform>-notify", "command": "./.prove/notify-<platform>.sh", "events": ["step-complete", "step-halted", "execution-complete"] } - Convert event selections to kebab-case slugs (e.g., "Step Complete" ->
step-complete)
Phase 6: Verification
- Run the script with
--test - Report success or failure
- Summarize: platform, scope, script path, subscribed events, config entry
Committing
Delegate to the commit skill.
Example: feat(notify-setup): add Slack webhook notification script
Related Skills
mjmorales/janitor
tools
VerifiedTrustedCommunity
Clean and compact prove's durable memory layers — team Lore, the Codex (scrum decisions), annotations, and contributor artifacts — keeping the tribal knowledge that grows team accuracy and folding away the rot. Triggers on "janitor", "clean the lore", "compact the lore", "compact the codex", "memory cleanup", "clean up team memory", "prune stale decisions", "tidy tribal knowledge", "lore cleanup". You are the driver: the CLI emits inventories and executes writes; the `memory-janitor` agent judges each entry; a per-team batch gate approves; nothing is ever deleted — consolidation, promotion, and supersession only.
2SKILL.mdUpdated Jun 9, 2026
mjmorales/smart-compaction
testing
VerifiedTrustedCommunity
Anchor session context into prove primitives before compaction and rehydrate from them after. Built-in compaction summarizes by recency and drops the claude-prove state an agent needs to reorient; this skill externalizes volatile context into durable anchors (scrum tasks, decisions, run-state, a compact-anchors pointer file) pre-compact, then runs a deterministic reorientation sequence post-compact. Use before a manual /compact, when context is about to auto-compact, or immediately after a compaction. Triggers on "smart compact", "prepare for compaction", "anchor before compact", "context is getting long", "rehydrate", "reorient after compact".
2SKILL.mdUpdated Jun 5, 2026
mjmorales/run-migrate
tools
VerifiedTrustedCommunity
Apply model-driven CONTENT reshaping to stored run artifacts that sit behind the current schema, on explicit operator invocation only. Triggers on "migrate runs", "migrate run artifacts", "run content migration", "reshape run artifacts", "bring runs to current schema". You are the driver: the `run-state migrate-runs` CLI mechanically detects which artifacts are behind and emits a plan naming each one plus its migration-instruction file; you read the instructions and reshape the prose/findings, gated by the operator. The deterministic `schema migrate` handles structural column moves; this skill covers only the content reshaping beyond them. Never run as a background or resident loop — only when the operator asks.
2SKILL.mdUpdated Jun 5, 2026
mjmorales/reasoning-brief
tools
VerifiedTrustedCommunity
Synthesize the 7-section risk-forward Review Brief from a run's reasoning log. Triggers on "reasoning brief", "review brief", "synthesize the brief", "generate the brief", "brief the run", "brief for review", "story brief". You are the driver: the `acb brief` CLI renders a mechanical preservation-safe backbone and proves preservation; you synthesize the narrative prose (summary + changes), single-pass or multipass over episode chunks, then gate it through Stage-1 (mechanical, blocking) and Stage-2 (prose judge, advisory).
2SKILL.mdUpdated Jun 5, 2026