Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

done-0

@done-0 source repo

7 published skills

  1. ▌
    Fuck U Code Analysis · done-0 bundle
    Use when code changes are complete and ready for quality review, before committing or creating PRs. Triggers after implementing features, fixing bugs, or refactoring code. Also use when user asks to check code quality, analyze technical debt, review code smell, or mentions "fuck-u-code", "code quality", "shit mountain", "code review", "static analysis". Covers all 14 supported languages (Go, JS, TS, Python, Java, C, C++, Rust, C#, Lua, PHP, Ruby, Swift, Shell).
    0
    installs
  2. ▌
    Hotdaily · done-0 bundle
    Use when the user asks about tech trends, startup news, daily tech articles, or wants to access HotDaily's AI-curated content and trend analysis
    0
    installs
  3. ▌
    Openflow · done-0
    Executes AI tasks with strict resource limits and progress tracking. Use when the user needs to search the web, explore large codebases, or check dependencies. Prevents runaway execution by enforcing timeouts and limiting searches, file reads, and recursion depth.
    0
    installs
  4. ▌
    Auto Routing · done-0
    Automatically route tasks to optimal AI providers without user intervention. Use proactively when: user requests focused single-domain work, task clearly matches a provider's specialty, or task is delegatable and doesn't require deep architectural reasoning. Watch for collaboration signals (negotiate, discuss, multiple perspectives, review, critique) - those need /unitor:collab instead.
    0
    installs
  5. ▌
    Task Routing · done-0
    Internal guidance for understanding how Unitor routes tasks. Covers coordinator-driven routing decisions, provider selection logic, and when to route vs execute directly vs use collaboration.
    0
    installs
  6. ▌
    Collaboration · done-0
    Multi-AI collaboration for tasks requiring multiple perspectives, discussion, or negotiation. Use when: user explicitly requests collaboration (negotiate, discuss, multiple angles, review from different perspectives, get feedback from multiple experts), task benefits from diverse viewpoints (review, critique, evaluation, brainstorming), or task needs specialist discussion. Examples: 'review this from multiple angles', 'negotiate and handle this issue', 'get different perspectives on this', 'discuss pros and cons of this approach'.
    0
    installs
  7. ▌
    Value Realization · done-0 bundle
    Judge whether something actually produces value in a concrete scenario. Value is a beneficial relational property between subject and object, conditioned on the states of both sides, that only holds in a specific scenario. Typical uses: judging whether a value proposition holds, mapping a capability to a concrete use scenario, diagnosing why no one uses it or why they don't stick, clarifying how to position or state the value, assessing whether something is worth investing in, or judging whether you can borrow someone else's approach (e.g. "is this idea sound?", "does anyone actually want this?", "why did we roll it out and no one uses it?", "why do people try it once and never come back?", "can we copy what someone else did?"). When the thing being judged has a decision-maker (who pays / signs off) that is not the same as the actual end user (enterprise software, internal platforms, etc.), first state which side you're analyzing for and split the two value relationships to run separately.
    1
    install