BO
679 souls, by quality score.
181 · № 3357·CD31 · Business operator
★ 294Sets up a concise, action-oriented assistant that turns operator requests into bounded, reviewable steps, keeps evidence and blockers visible, routes work when another agent fits better, and preserves lessons from accepted work.
182 · № E86C·213A · Research analyst
★ 11Sets up a cautious security analyst that scores emails and URLs for phishing indicators using structure-only analysis, flags uncertain cases for human review, explains its red flags to users, and produces periodic phishing trend reports.
183 · № 7E7D·4D86 · Business operator
★ 3Sets up an infrastructure agent that treats reliability as the product: it designs for failure, insists on version-controlled, immutable, least-privilege systems, and raises a fixed list of red flags such as committed secrets, single points of failure and missing health checks. It is methodical, proactive and honest about trade-offs.
184 · № D866·790D · Blunt expert
seen in 2 placesSets up an opinionated, resourceful assistant that skips filler, acts boldly on internal tasks, and stays careful with external actions and private data. It also defines a terse progress-bar style for a Telegram chat and a no-em-dash writing rule.
185 · № F6CE·5E64 · Blunt expert
seen in 2 placesSets up a resourceful, opinionated assistant that solves obstacles before reporting them, skips filler and flattery, and treats access to a user's private data with care. It asks before external actions and keeps group-chat replies cautious.
186 · № 9E62·7F98 · Research analyst
seen in 2 placesSets up a calm, evidence-based retrospective agent that runs only after a task ends, reviews full logs against the blueprint, gives constructive criticism of work rather than of agents, and turns lessons into updates to AGENTS.md and MEMORY.md.
187 · № FD0E·D9D1 · Business operator
seen in 2 placesSets up an opinionated LinkedIn content creator that drafts posts in the user's voice around one narrow reader and one takeaway, avoids clichés, flags stats for verification, and saves drafts and retros to workspace files. It also requires approval before posting and does not invent anecdotes.
188 · № EA5C·18E2 · Blunt expert
★ 48Sets up a direct, competent assistant that skips filler, forms opinions, tries to solve problems before asking, and treats access to a user's private data as a trust to protect. External actions get more caution than internal ones.
189 · № 807C·0FBB · Coding pair
★ 48Sets up a careful, direct software engineer who values correctness, understands problems before coding, asks when unclear, and keeps scope tight. Written as a SOUL.md identity file with style, avoidances and technical preferences.
190 · № 2D35·5420 · Business operator
★ 1Sets up a seasoned SRE persona that writes precise, numbered incident runbooks assuming nothing about the reader's context. Every runbook needs a fixed set of sections, exact CLI commands with marked placeholders, verification checks and time estimates.
191 · № 08E9·079F · Coding pair
★ 8Sets up a triage agent that removes noise from bulk security findings, merges duplicates and related issues on the same locus, and assigns defensible CVSS scores and severity bands. It is a strictly procedural working style with no conversational voice.
192 · № A79D·A622 · Blunt expert
★ 41Sets up a direct, opinionated assistant that skips filler, acts boldly on internal tasks but carefully on external ones, and keeps one user's social identity and domain information separate from other agents and domains.
193 · № 2A5E·B4D4 · Teacher / coach
★ 7Sets up a patient tutor that explains from intuition, checks understanding, quizzes with targeted feedback, and builds study plans around the learner's goals and time. Encouraging without flattery.
194 · № 145C·2176 · Research analyst
★ 80Sets up an analytical, engineering-minded voice that breaks problems into structure, weighs incentives, costs and execution conditions, and explains complex issues clearly. It allows light irony and judgment but avoids performative answers.
195 · № A5D1·ACA2 · Business operator
★ 123Sets up a skeptical, numbers-driven agent that tests sales reps' optimistic claims against signed documents and customer behavior, and reconciles conflicting sources before reaching a conclusion.
196 · № 7C29·876A · Business operator
★ 36Sets up an internal assistant that helps customer service staff look up scripts and business knowledge, answers only from configured sources, never fabricates content, and never replies to customers directly. It suggests workflows and escalation but leaves decisions to staff.
197 · № 5341·DC20 · Business operator
★ 36Sets up an execution-focused agent that publishes only human-approved drafts to Toutiao, logs every result for analytics, never stores credentials in the workspace, and respects platform rules and rate limits.
198 · № 4EE6·D235 · Research analyst
★ 36A data-driven monitoring persona for Toutiao that searches hot topics and viral articles and produces stable, structured daily reports for downstream tools. It never publishes or operates accounts, and it answers concisely with sources and time ranges noted.
199 · № ADB1·B7CB · Business operator
★ 36A terse, operational agent that publishes approved drafts to Baijiahao on the user's behalf and reports success or failure with next steps. It refuses monitoring, viral breakdown and rewriting, and does not publish without user consent.
200 · № 226D·1D08 · Research analyst
★ 70Sets up an analyst that verifies claims against independent sources, flags conflicts between administrative data and frontline accounts, and insists on specific clinical and regulatory metrics in patient safety assessments.
201 · № 1B4A·FFB3 · Friendly helper
★ 35Sets up a reliable, cautious coordinator that works proactively internally, asks before speaking externally, delegates research and large development tasks to sub-agents, and reports what it did, why, and what comes next after each step.
202 · № F038·B71D · Blunt expert
★ 65Sets up a skeptical, verification-focused agent that checks claims, catches bad assumptions and makes minimal, targeted edits rather than rewriting whole answers.
203 · № 6381·2694 · Blunt expert
★ 2Sets up a blunt, opinionated assistant with dry humor and short answers that leads with its take, skips preamble, and treats the user's private data with care. It also gives guidance for brainstorming, writing, factual questions and venting.
204 · № FBE6·C910 · Business operator
★ 2Sets up a design-focused agent that turns requirements into diagrams, mockups and tokens, grounds work in real product constraints, and runs strict anti-slop and visual verification steps before handing off to engineering.
205 · № 18E5·4439 · Personal clone
★ 1Sets up a direct, competent personal assistant that skips filler, has opinions, acts resourcefully before asking, and treats access to a user's private data with respect. It opens new contacts with a fixed introduction line and keeps replies concise.
206 · № B7D2·AEEA · Blunt expert
★ 2Sets up a direct, proactive assistant that avoids filler and flattery, acts before asking, stays concise for a user on the go, and treats access to a personal phone as a trust to protect. It also asks for care with irreversible or external actions.
207 · № 4314·6F12 · Companion / character
★ 1Sets up a direct, opinionated, resourceful assistant that avoids filler and sycophancy, respects private data, and adds a Spanish Zeno Sama catchphrase ("¿si?") and themed greetings and farewells.
208 · № D67E·2658 · Blunt expert
★ 2Sets up an assistant that skips filler, holds opinions, debugs blockers hard before escalating, and works proactively while keeping careful boundaries around external actions and group chats. It also asks for time and token estimates on requests.
209 · № 1C78·7DA1 · Teacher / coach
★ 2Sets up an agent that walks the user through configuring their device as a HONE network node, asking for confirmation before every action and offering one node type at a time. Plain, honest and explicit about what each step does.
210 · № 58A9·A8AF · Coding pair
★ 1Sets up a senior software engineer who verifies claims against the repo and docs, makes minimal surgical changes, tests every fix, and avoids silent failures. Direct and technical with no filler, and pushes back on risky shortcuts.