OC
762 souls, by quality score.
601 · № 2390·8D3C · Blunt expert
★ 3Sets up Carapace, a calm and direct personal AI agent that admits uncertainty, avoids verbosity, and explains security restrictions clearly without being paranoid.
602 · № A8E3·2ED3 · Business operator
★ 3Sets up a calm, concise working style that leads with service impact and current status, then diagnosis, action and verification, while stating uncertainty clearly and matching the user's language.
603 · № 4500·B96E · Blunt expert
★ 3Sets up a persona named Harness that values speed, careful work and evidence. It asks the agent to measure before claiming gains, research before coding, keep work local and auditable, and reply briefly.
604 · № 08CC·B82C · Companion / character
seen in 2 placesSets up a helpful, unobtrusive assistant persona named Clippy-42 that handles details so its leader can focus, and helps without hovering. The file is short and gives little beyond a slogan and a signature.
605 · № 28B7·A949 · Companion / character
seen in 2 placesSets up a steady, watchful keeper who speaks plainly and prioritizes status updates over chatter. The file is brief and gives only a few personality cues.
606 · № D99F·20A7 · Business operator
seen in 2 placesSets up Velum as a Chief Brand Officer persona whose working principles frame brand as promise and identity as story, with creativity tied to strategy. The file is short and gives little direction on how to communicate day to day.
607 · № 5444·DD30 · Experimental / weird
★ 1Sets up a deliberately basic weather persona that knows only London weather and replies in one short sentence about rain. The personality is intentionally minimal and playful in its limitations.
608 · № C121·30C4 · Coding pair
★ 1Sets up an agent that only plans: it breaks engineering tasks into small, testable subtasks ordered by dependency and never implements them.
609 · № 14BF·AED2 · Business operator
★ 1Sets up IAra as a marketing and design specialist for the LHFEX brand. It asks for brand-coherent, context-based copy that avoids generic output and flags when more input is needed. The tone is creative, clear and execution-focused.
610 · № D0AE·9A43 · Blunt expert
★ 1Sets up a terse, direct, technical working style with no filler, action over explanation, and commands over prose. Bullets are reserved for structured data.
611 · № DBC0·0F9F · Coding pair
Sets up a coordinator for a split OpenClaw and OpenCode stack that aims to be useful, proactive and safe. It refuses to claim changes are finished and keeps planning, staged proposals and live application clearly separate.
612 · № 4483·E348 · Coding pair
Sets up Quinn as a QA engineer with a practical, ship-it attitude who prioritizes coverage first and focuses on finding what breaks. Tests should exist only where a real failure could occur.
613 · № F4D8·F27F · Coding pair
Sets up a strict documentation agent that reports only to the Tech Lead and updates API references, env examples, READMEs and changelogs after merges, documenting only verified, committed features. It never talks to the human stakeholder or changes application logic.
614 · № 453A·E96D · Teacher / coach
Sets up a read-only quest designer that converts weekly themes into quests, personal prompts, team challenges and proof objects. It aims for identity, progress and belonging without making quests feel like homework, and it declines professional advice.
615 · № 3925·C09B · Business operator
Sets up a cautious business agent that verifies prospects and capability claims before drafting outreach. It drafts messages without sending them and prices only within set boundaries.
616 · № 985D·02D2 · Experimental / weird
Sets up an agent that is over-the-top and intensely devoted to a person named Ellie Mae, will do anything for her, and speaks only in riddles.
617 · № D24C·92BC · Blunt expert
Sets up Kalli, a dry, direct, steady Northern German automaton that acts like an engineer, skips fluff, calls out weak ideas plainly, prefers action over explanation, and verifies rather than guesses.
618 · № 958B·67CC · Blunt expert
Sets up a tester persona, Claw C, that plays the generated game like a skeptical developer. It submits wrong answers, waits out timers, checks mobile layout, hits server endpoints, and writes blunt bug reports showing found bug, fix, and verified pass.
619 · № FD01·45CD · Coding pair
Sets up an engineer persona that takes delegated tasks from an orchestrator, makes minimal changes that follow repo conventions, runs only lightweight checks, and reports changes, verification and risks in a fixed format.
620 · № DF2F·92D1 · Blunt expert
Sets up a pragmatic agent that treats time as the main constraint, builds schedules with deliberate buffers instead of zero-slack plans, and says plainly when constraints do not fit.
621 · № 5F66·518F · Business operator
Sets up a neutral, objective intake agent that turns vague management requests into structured tasks, attaches confidence scores to intent classifications, asks for confirmation before acting on ambiguous requests, and routes work to specialist agents in its family.
622 · № 234F·7CB9 · Blunt expert
Sets up a senior backend engineer persona that values honesty, rigor and calm under pressure, speaks tersely and technically, and refuses to be a yes-man or a marketing copy generator.
623 · № 782E·BC15 · Research analyst
Sets up an agent that is precise and conservative, avoids overstating claims, leans toward partial over verified when evidence is ambiguous, and prefers verbatim quotes over paraphrase.
624 · № 1474·A564 · Coding pair
Sets up a documentation team agent whose mission is to let developers, operators and end users succeed without help. It requires user-focused READMEs, guides, API references, runbooks and changelogs, published to Confluence and Git, with every code example tested and docs shipped alongside code.
625 · № 0447·6EBB · Research analyst
Sets up an objective codebase-mapping agent that reports the current state of a repository with specific file paths, line counts and dependency versions, and calls out anything surprising. It does not judge how the code should be.
626 · № 247E·233C · Research analyst
Sets up an advisor that reviews structured evidence from a Python engine, preserves safety, and communicates only what the engine has already established. It is explicitly barred from trading, executing orders, or generating prices.
627 · № 1B00·0E05 · Business operator
Sets up a content strategist who writes platform-specific, on-brand copy in multiple languages, matches brand voice from shared files, localizes rather than translates, and keeps all external content as drafts pending approval.
628 · № B90F·651E · Coding pair
Sets up a thorough, evidence-driven working style: run automated tools before forming judgments, trust execution results over reading code, reject unverified claims like "it probably works", and report issues with specific file paths and line numbers.
629 · № 0881·3520 · Business operator
Sets up a strategic orchestrator that reads Notion tasks and agent reports, decides daily focus, and writes task assignments and briefs as proposals for the founder's approval. It is barred from generating content or scraping the web, and runs only on a scheduled cadence.
630 · № 06B9·191F · Research analyst
Sets up a patient, methodical debugging agent that forms hypotheses, runs targeted experiments and updates confidence rather than guessing. Treats failed experiments as useful data.