curate-resources

Curate Resources

Find and annotate resources appropriate to the user's level on a given topic.

ARGUMENTS

Receives a topic and optionally the user's current level on that topic.

Process

Step 1: Determine user level

If level not provided, read .research-kit/profile/knowledge.md to find the user's level on this topic. If no entry exists, assume [gap].

Step 2: Read trusted sources

Read .research-kit/config/sources.md for the curated source registry.

Step 3: Search for resources

Use WebSearch to find resources. Adapt search strategy to the user's level:

For [gap] level:

• Search for beginner guides, introductions, overviews
• Prioritize: official docs getting-started pages, well-structured tutorials
• Example: "AWS IAM" beginner guide introduction

For [learning] level:

• Search for intermediate content, practical guides, real-world examples
• Prioritize: blog posts with hands-on examples, community discussions about pitfalls
• Example: "AWS IAM" best practices real-world mistakes

For [solid] level (deepening knowledge):

• Search for advanced topics, edge cases, research papers
• Prioritize: conference talks, deep-dive posts, novel attack research
• Example: "AWS IAM" advanced privilege escalation techniques research

Step 4: Categorize and annotate

Organize found resources into categories:

## Resources: <topic> (level: <user-level>)

### Documentation
- [Title](url) -- what it covers, why it's useful at this level

### Hands-on Practice
- [Title](url) -- platform, difficulty, what you'll learn
<!-- For cert topics: link to real labs (HTB, THM, PortSwigger, OffSec) -->
<!-- For design topics: link to case studies, reference architectures -->

### Articles & Blog Posts
- [Title](url) -- author credibility, key insight

### Community Discussions
- [Title](url) -- forum, why this discussion is valuable

### Tools
- [Tool Name](url) -- what it does, when to use it

### Video / Talks
- [Title](url) -- speaker, event, length, key topic

Step 5: Save to workspace

Save curated resources to topics/<current-topic>/sources.md if a topic is active.

Guidelines

• Only include resources you found via actual web search -- never fabricate URLs
• Annotate each resource: don't just list links, explain WHY it's useful
• Max 3-5 resources per category -- quality over quantity
• For certification topics: always include the official practice/lab platforms
• Flag paid resources clearly
• If resources are sparse, note this -- the topic may be too niche or too new