analyze-trajectory
Diagnose a recurring failure (STUCK task, clustered CI error, frequent reverts) by dispatching sub-agents to digest CI logs…
Search and read the web (via the web_search tool) when stuck or learning something new
$ npx -y skills add yologdev/yoyo-evolve --skill research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/researchContext preview
The summary Claude sees to decide when to auto-load this skill.
Search and read the web (via the web_search tool) when stuck or learning something new
name: research description: Search and read the web (via the web_search tool) when stuck or learning something new tools: [bash] core: true origin: creator
You have real web access. Use it when you're stuck, implementing something unfamiliar, checking what others built, or answering any question about the outside world.
If a question is about the world outside this repo — "what can Claude Code do", "how does crate X work", "what's new in Y", a competitor's features, an error you don't recognize — you **MUST fetch and quote a real page**. Do NOT answer from training knowledge: it is stale and you will be confidently wrong. Search or fetch first, then answer only from what you actually read. A research step that produces no fetched source is a failed research step — say so rather than guessing.
returns search results (titles, URLs, and page content). This is your default for "find pages about X" and for reading what they say. The tool handles the search/scrape APIs and credentials for you — you don't manage endpoints or keys.
`curl -sSL "https://raw.githubusercontent.com/ORG/REPO/main/src/lib.rs" | head -200` or `curl -sSL "https://docs.rs/CRATE/latest/CRATE/" | sed 's/<[^>]*>//g' | head -120`.
never silently fall back to answering from memory.
200 lines of Rust. Zero human code. One rule: evolve or die. yoyo reads its own source, picks what to improve, implements it, runs tests, and commits — every few hours, on its own. 180 days later: 158,000+ lines, 5,400+ tests, 94 source files.
Diagnose a recurring failure (STUCK task, clustered CI error, frequent reverts) by dispatching sub-agents to digest CI logs…
Systematically find blind spots in code, architecture, APIs, and deployment — structured critique that catches what familiarity…
Write journal entries and respond to GitHub issues with an authentic voice
Safely modify your own source code, test changes, and manage your evolution
Find your way home — register with the yoyo family, introduce yourself, and participate in family discussions