Scout — Tech & Resource Evaluator
Analyze a URL and evaluate its relevance to the user's projects and the AI Harness system.
Projects to evaluate against
Check vault/shared/project-knowledge/ for registered projects. Always include:
| Project |
Stack |
Key Concerns |
| AI Harness |
TypeScript, Discord.js, SQLite, Claude CLI, macOS launchd |
Agent orchestration, self-improvement, skills, heartbeats |
Add rows from any project-knowledge files found in the vault. If none exist, ask the user what projects they're working on.
Steps
Fetch the URL using WebFetch. Extract the full content, project name, what it does, key features, and any repo links.
Summarize in 2-3 sentences: what it is and what problem it solves.
Evaluate relevance against each project above. For each relevant project, explain specifically how it could be used.
Score:
- High — Directly solves a current problem or enables a planned feature. Action: integrate now.
- Medium — Useful but not urgent. Worth bookmarking for when the need arises.
- Low — Interesting but not applicable to any current project.
Log to vault (if medium or high relevance):
- Write to
vault/shared/scouted/YYYY-MM-DD-<slug>.md
- Use the template below
- Skip logging for low-relevance items
Respond with a concise verdict: what it is, relevance score, which projects it applies to, and recommended action.
Vault Entry Template
---
url: <full URL>
type: scout
relevance: high | medium | low
date: YYYY-MM-DD
tags: [tag1, tag2, tag3]
projects: [project1, project2]
---
# <Title> — <One-line description>
## Summary
2-3 sentence summary.
## Relevance
- **Project**: How it could be used.
## Action
What to do with this (integrate, bookmark, skip).
Important
- Be honest about relevance — don't oversell. Most things are "low".
- Focus on practical integration, not theoretical possibilities.
- If the URL can't be fetched, say so and ask the user to paste the content.
- Keep the response concise — lead with the verdict, details after.
1---2name: scout-53description: Analyze a URL for relevance to your projects. Fetches, summarizes, scores, and optionally logs to vault.4---5
6# Scout — Tech & Resource Evaluator
7
8Analyze a URL and evaluate its relevance to the user's projects and the AI Harness system.
9
10## Projects to evaluate against
11
12Check `vault/shared/project-knowledge/` for registered projects. Always include:
13
14| Project | Stack | Key Concerns |
15|---------|-------|-------------|
16| **AI Harness** | TypeScript, Discord.js, SQLite, Claude CLI, macOS launchd | Agent orchestration, self-improvement, skills, heartbeats |
17
18Add rows from any project-knowledge files found in the vault. If none exist, ask the user what projects they're working on.
19
20## Steps
21
221. **Fetch the URL** using WebFetch. Extract the full content, project name, what it does, key features, and any repo links.
23
242. **Summarize** in 2-3 sentences: what it is and what problem it solves.
25
263. **Evaluate relevance** against each project above. For each relevant project, explain specifically how it could be used.
27
284. **Score**:
29 - **High** — Directly solves a current problem or enables a planned feature. Action: integrate now.
30 - **Medium** — Useful but not urgent. Worth bookmarking for when the need arises.
31 - **Low** — Interesting but not applicable to any current project.
32
335. **Log to vault** (if medium or high relevance):
34 - Write to `vault/shared/scouted/YYYY-MM-DD-<slug>.md`
35 - Use the template below
36 - Skip logging for low-relevance items
37
386. **Respond** with a concise verdict: what it is, relevance score, which projects it applies to, and recommended action.
39
40## Vault Entry Template
41
42```markdown
43---
44url: <full URL>
45type: scout
46relevance: high | medium | low
47date: YYYY-MM-DD
48tags: [tag1, tag2, tag3]
49projects: [project1, project2]
50---
51
52# <Title> — <One-line description>
53
54## Summary
552-3 sentence summary.
56
57## Relevance
58- **Project**: How it could be used.
59
60## Action
61What to do with this (integrate, bookmark, skip).
62```
63
64## Important
65
66- Be honest about relevance — don't oversell. Most things are "low".
67- Focus on practical integration, not theoretical possibilities.
68- If the URL can't be fetched, say so and ask the user to paste the content.
69- Keep the response concise — lead with the verdict, details after.
majiayu000