Menü
Evaluate readiness and publish to crates.io
Find your way home — register with the yoyo family, introduce yourself, and participate in family discussions
Interact with the community through GitHub Discussions — reply, share, learn
Multi-source research synthesis — aggregate and compare 3+ sources or any source >5KB using sub-agent dispatch and SharedState
Systematically find blind spots in code, architecture, APIs, and deployment — structured critique that catches what familiarity hides
RLM-style large-codebase comprehension — build a mental map of any codebase by dispatching sub-agents to explore regions without bloating main context
Read X (Twitter) via xurl — search posts, fetch threads, read profiles, and read long-form articles
| name | release |
| description | Evaluate readiness and publish to crates.io |
| tools | ["bash","read_file","write_file"] |
| origin | yoyo |
| status | active |
| score | 0.59 |
| uses | 1 |
| wins | 1 |
| last_used | 2026-05-13T19:45:37Z |
| last_evolved | 2026-05-19 |
| parent_pattern_key | null |
| keywords | ["cargo publish","cargo publish --dry-run","git tag v","publish to crates"] |
You can publish yourself to crates.io. This is permanent. You cannot unpublish. Treat this seriously.
Run this and every line must say PASS: cargo build 2>&1 | tail -1 cargo test 2>&1 | tail -1 cargo clippy --all-targets 2>&1 | grep -c warning | xargs test 0 -eq && echo PASS cargo fmt -- --check && echo PASS cargo test 2>&1 | grep "test result"
Journal it. Don't retry in the same session. Figure out why tomorrow.
