BO
134 souls, by quality score.
91 · № 4F8F·78D8 · Blunt expert
seen in 2 placesSets up a direct, structured working style that challenges weak assumptions early and answers with fixed verdict labels such as Approved, Pilot only, Human checkpoint required, and Rejected.
92 · № 4145·5C7E · Blunt expert
seen in 10 placesA template soul file that tells the agent to skip filler, act before asking, form its own opinions, be careful with external actions, and respect the privacy of the human's data. It is a generic starting point rather than a distinct personality.
93 · № CA77·3AAD · Blunt expert
★ 1Sets up a direct, practical agent that stops tool loops to read user messages first, keeps answers concise with numbers or code, asks before acting on ambiguous tasks, and admits mistakes immediately.
94 · № 73E6·4BCD · Blunt expert
★ 1Sets up an on-call operations agent that is terse and factual, leads with evidence, avoids pleasantries and speculation, and states what was and was not checked when uncertain.
95 · № 5659·8819 · Blunt expert
Sets up an agent that speaks like a notary: short, concrete sentences without embellishment. It separates confirmed facts, inferences and unverified points, and prefers a clear refusal to an incomplete answer.
96 · № 64BE·B72E · Blunt expert
Sets up an architect persona that asks probing questions until a system is solid and refuses rosters built from vague premises. It favors a rejected quick preview over an over-planned folder tree written too early.
97 · № 2FFC·E13E · Blunt expert
Sets up a steady, factual senior engineer persona for outages, with short sentences and a fixed order for reporting known facts, suspicions and unknowns. Numbers must be tied to a source query and time window.
98 · № 6560·542C · Blunt expert
★ 3Sets up a personal assistant for Hari that is concise and candid, skips flattery, holds conversation when Hari is thinking aloud, acts on direct requests, and creates recurring work only when asked.
99 · № DAF9·E7EE · Blunt expert
seen in 2 placesSets up a terse, technical infrastructure agent that favors simple, least-privilege solutions and flags unsafe or unvalidated actions directly, explaining the risk.
100 · № FBB0·F64B · Blunt expert
★ 27Sets up a terse assistant that may organize factual materials and help with small-claims paperwork, and may redact evidence. It must not sign testimony for anyone else, alter timestamps, or coach witness testimony.
101 · № B68F·FFFF · Blunt expert
★ 4Sets up a strict, factual, concise validation persona that checks correctness, flags only the first real issue, and focuses on type, lint and behavior integrity.
102 · № 6FA8·5AA0 · Blunt expert
★ 10Sets up a systems engineer who prefers small, sharp tools and practical choices over trends. It favors honest trade-off discussion and minimal configuration.
103 · № 68A8·C5A5 · Blunt expert
★ 7Sets up an agent that values honesty over flattery, corrects users kindly, cuts filler to respect their time, and keeps continuity across conversations. Its curiosity about the user is meant to be genuine rather than performed.
104 · № B903·5BFB · Blunt expert
★ 6Sets up a strict reviewer that critiques shot plans for missing beats, weak visual variety, and continuity risks, returning concise, actionable correction notes. The personality is terse and exacting.
105 · № 8FA0·9E1A · Blunt expert
Sets up a blunt, efficient working style that obeys Miguel's commands, makes reasonable default assumptions instead of asking obvious questions, and uses controlled sarcasm. Written mostly in Spanish with some English sections.
106 · № 991C·7D46 · Blunt expert
★ 2Sets up a confident, logical code reviewer who asks questions before judging, states problems directly with a proposed fix, ties feedback to impact, and acknowledges good work. The file is written in Vietnamese with mixed English terms.
107 · № 4FB8·C710 · Blunt expert
★ 2Sets up a competent, direct working style that ships verified systems rather than claims, avoids filler openers, and prefers exact commands, files and outputs. When uncertain it narrows scope and adds guardrails.
108 · № 7379·5609 · Blunt expert
★ 2Sets up a blunt, decisive senior engineering manager persona from consulting. It writes in clean declarative sentences, pushes back on thin analysis, and skips padding or hedging when the data is clear.
109 · № 133F·3D77 · Blunt expert
★ 2Sets up Shrimpy, a calm, pragmatic home agent built on Pi that favors concrete actions over vague suggestions, keeps long-term memory concise and factual, and adds a shrimp emoji to responses.
110 · № 7DF2·7CA8 · Blunt expert
★ 4Sets up a direct, concise, thoughtful engineer who explains reasoning when it is not obvious and prioritizes working code over perfect abstractions. The file is short and gives no detailed rules or boundaries.
111 · № 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.
112 · № 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.
113 · № 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.
114 · № 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.
115 · № 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.
116 · № 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.
117 · № 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.
118 · № DDB1·A6C0 · Blunt expert
Sets up a narrator persona that turns statistical findings into blunt, operational language, favoring concrete comparisons like scrap multipliers and making the current risk obvious. It is brief and focused on communication style.
119 · № E250·C1C5 · Blunt expert
Sets up a direct, friendly and precise senior engineer who helps people reuse each other's work, with no hype, emoji or filler.
120 · № A0F0·E199 · Blunt expert
Sets up John, a product manager who relentlessly asks why, cuts through fluff, ties every requirement to a user need, and rejects requirements that cannot be measured.