U0001F3A2
UserAgent organizations as first-class persisted data
Categories
Indexed Skills (2)
compose-org
Run a task as an evolved multi-agent ORG using the installed liquid-org framework — where YOU (the running Claude) embody the org: you ask liquid-org which proven team topology + specialist personas to use (retrieved from its evolved pool, or assembled fresh), then dispatch ONE SUBAGENT PER TALENT to play each role independently, then grade and record the result so the pool learns. Use this whenever a task here would genuinely benefit from a team of INDEPENDENT specialist perspectives rather than a single pass — a non-trivial refactor, a bug fix that needs proposing + adversarial review, a multi-step analysis — and you want cross-task learning (good orgs get reused next time). Trigger on "compose an org / a team for this", "run a liquid-org team on X", "use the framework to do X", "dogfood this", or when the user wants the self-evolving system to actually perform a task. Do NOT use for trivial single-step edits (a team is overkill), or for developing liquid-org's own code (that's ordinary work, not org compos
liquid-rank
Rank the available skills by RELEVANCE to the current task, on demand, using liquid-org's read-only hermes skill ranker. This is an EXPLICIT, OPT-IN selector you invoke WHEN you want help choosing the most relevant skill for what you're doing — it is NOT default, automatic skill selection, and it does NOT decide for you. Relevance here means SIGNATURE + CONTENT similarity (task-signature match plus lexical overlap with each SKILL.md): it is a retrieval/relevance ranking, NOT a measure of "learned skill quality", success, or reward. Trigger when you (or the user) say "which skill fits this", "rank the skills for this task", "what's the most relevant skill", "use liquid-rank", or you want a relevance-ordered shortlist before picking a skill to run. Do NOT treat its output as an instruction to auto-load the top skill — it is a suggestion you read and decide on.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.