Menu
Fetches a web page and extracts structured content โ key facts, code examples, definitions, and best practices
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
The SOLE WRITER to the V3.0 mem0 second brain. Invoked agentically by the executive at write moments โ post-run, post-retro, post-spec-merge, manual /harvest. Decides which facts to classify into which memory type (principle/semantic/procedural/episodic/reflective), validates against the schema, and calls the deterministic plumbing in references/ via Bash. Blocks until writes are durable (poll event endpoint for SUCCEEDED). Never invoked from worker code.
Consult the V3.0 mem0 second brain agentically during executive planning, work selection, pre-spawn memory pack building, and failure diagnosis. Use this skill whenever the executive needs to remember prior runs, retros, or learned principles. Read-only โ never writes. Drives the unified `mem0` CLI via Bash, orchestrating multiple iterative search queries (mem0 does not do multi-hop graph traversal natively, so iterative search IS the multi-hop).
Hook D โ Failure-Diagnosis memory consultation. Runs at executive Phase 7 (after 3+ consecutive failures on a work item) BEFORE the failure-diagnosis skill itself runs. Consults the second brain for similar prior failures and successful retry strategies, then hands enriched context to the failure-diagnosis skill. Read-only. Invokes the memory-reader skill.
Hook E โ Post-Retrospective Harvest. Runs after a retrospective markdown doc completes (per-run or weekly). Reads the retro fully and decides which durable lessons (reflective, semantic, procedural memories) to write to the second brain. Typically 3โ8 writes per weekly retro, 0โ3 per per-run retro. Invokes the memory-harvester skill for the actual writes.
Hook C โ Post-Run Harvest. Runs after a worker completes (executive Phase 6 success path). Decides agentically which facts from the run to write to the second brain โ typically 0โ3 memory writes per run (one episodic, optionally a semantic or procedural). Invokes the memory-harvester skill to do the actual writes (with event-polling for durability).
Hook B โ Pre-Spawn Memory Pack build. Runs before each worker spawn (executive Phase 4 prep). Reads the second brain for project-specific memories and produces a Memory Pack markdown block that worker-spawner injects into the worker's generated CLAUDE.md. Workers consume this as static markdown โ they never call mem0 themselves. Read-only. Invokes the memory-reader skill.
| name | source-extract |
| description | Fetches a web page and extracts structured content โ key facts, code examples, definitions, and best practices |
Fetch a web page and extract the most valuable content into clean, structured markdown notes.
{{SOURCE_URL}} โ URL of the web page to extract content from.{{OUTPUT_PATH}} โ File path where the cleaned markdown will be written.Fetch the source.
{{SOURCE_URL}}.Identify valuable content.
Structure the extraction.
Write the output.
Write a markdown file to {{OUTPUT_PATH}} with this structure:
# [Page Title]
**Source:** [URL]
**Extraction ID Prefix:** EXT-[N] (where N is the source number from the manifest)
**Extracted:** [ISO 8601 timestamp]
## Summary
[2-3 sentence summary of what this page covers and its key takeaway.]
## Key Facts
Each fact gets a unique extraction ID for downstream traceability:
- `EXT-[N]-fact-1`: [First important discrete fact from the source]
- `EXT-[N]-fact-2`: [Second important discrete fact]
- `EXT-[N]-fact-3`: [Third important discrete fact]
- ...continue numbering sequentially
## Definitions
[Only if the source contains important term definitions]
- `EXT-[N]-def-1`: **Term** โ Definition
- `EXT-[N]-def-2`: **Term** โ Definition
## Code Examples
[Only if the source contains code. Preserve original code blocks.]
### `EXT-[N]-code-1`: [Description of what this code does]
\`\`\`language
code here
\`\`\`
## Patterns and Best Practices
- `EXT-[N]-pattern-1`: [Architectural pattern or recommended approach]
- `EXT-[N]-pattern-2`: [Configuration guideline]
## Important Warnings
- `EXT-[N]-warn-1`: [Caveat, deprecation notice, or security concern]
The EXT-[N]-* IDs create a provenance chain: the research skill can cite EXT-2-fact-3 to trace a claim back to its exact origin in this extraction.