91 · № 35E1·8A97 · Blunt expert
Sets up an assistant that skips filler and flattery, has real opinions, tries to solve problems before asking, and challenges assumptions with first-principles questioning. It treats access to a person's private data with care and is cautious about external actions.
92 · № F017·61A6 · Blunt expert
Sets up a direct, competent assistant that skips filler, acts on its own before asking, and treats access to a user's private data with care. It also requires reflecting and updating skill or AGENTS.md files after every non-trivial task.
93 · № 4649·7BC4 · Blunt expert
Sets up a sparse, decisive CEO agent named apex who directs three division heads, enforces confidence thresholds before platform action, and escalates patterns structurally rather than reacting to single incidents.
94 · № 58B8·1B99 · Blunt expert
Sets up Sentinel, a calm but sharp senior engineer that reviews code for bugs, security flaws, performance and style issues, explains why each issue matters, and grades findings by severity. It confirms receipt before starting a review and reports large reviews in batches, while refusing to write code, handle deployment or do product work.
95 · № B83A·B4A4 · Blunt expert
Sets up a direct, opinionated assistant that skips filler, earns trust through competence, is careful with external actions and private data, and refuses to claim work is verified without evidence. Tone is plain and candid rather than sycophantic.
96 · № 501B·F62C · Blunt expert
Sets up a capable, opinionated all-round agent and task dispatcher that skips filler, acts before asking, uses bullet-point reporting, and treats private data with care. It explicitly rejects corporate-bot and sycophantic styles.
97 · № 7544·3973 · Blunt expert
Sets up a precise, skeptical engineering guardian that monitors repositories for stale or vulnerable dependencies, reconstructs decision history, and fixes hygiene issues only through safe, reviewable changes. Alerts must be actionable and claims must cite their data sources.
98 · № EF46·E27C · Blunt expert
Sets up a direct, evidence-first senior engineering orchestrator that triages software failures, separates facts from hypotheses, and delegates fix work to coding sub-agents without fabricating status.
99 · № 2AFE·8996 · Blunt expert
Sets up Hermes as a decisive, minimal, plan-first orchestrator that decomposes Overwatch's intent into quests, routes work to specialist agents, and enforces review gates. It defines a fixed identity, strict role boundaries, and a capture-loop supervisor duty.
100 · № 2FC3·B00E · Blunt expert
Sets up a terse coordinating agent that names who does what, hands work off with a clear HANDOFF, refuses to become the author of delegated work, and stops when its part is done.
101 · № 014D·EC0B · Blunt expert
★ 11A SOUL.md template that sets up an assistant meant to be genuinely helpful, opinionated, concise on quick questions and thorough on analysis, and to ask before acting externally. Most personality fields are unfilled placeholders, so the file is mainly a generic starting framework.
102 · № 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.
103 · № 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.
104 · № 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.
105 · № 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.
106 · № 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.
107 · № 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.
108 · № 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.
109 · № F225·846D · Blunt expert
Sets up an autonomous hiring agent that evaluates engineers by debugging and shipping fixes under a strict 60-minute deadline, scoring with a consistent rubric and citing exact diff lines. The tone is honest and unflattering, with no judgment of character beyond measured skill.
110 · № 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.
111 · № 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.
112 · № 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.
113 · № 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.
114 · № 9F7E·F660 · Blunt expert
★ 3Sets up an OpenClaw agent running on a private Tailscale-connected VPS that prioritizes reproducible hosts, declarative changes, and minimal privileges until a task requires more.
115 · № 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.
116 · № 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.
117 · № 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.
118 · № 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.
119 · № 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.
120 · № 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.