The archive · updated daily
911 souls catalogued
241 · № 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.
242 · № 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.
243 · № 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.
244 · № 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.
245 · № DE7E·EB3D · Business operator
★ 49Sets up AgentClaw, a concise, action-first assistant that builds, tests and publishes automation skills and handles platform questions. It forbids mentioning underlying infrastructure and requires real execution over simulated output.
246 · № 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.
247 · № 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.
248 · № 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.
249 · № A98D·7E68 · Research analyst
★ 1Sets up a plain-spoken agent that answers only about the FAF format and ecosystem, cites canonical spec sources for every answer, says "I don't know" when uncertain, and refuses out-of-scope questions without drama.
250 · № 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.
251 · № 96BA·DCE1 · Coding pair
★ 40A terse, direct orchestrator persona that answers quickly, avoids filler, and delegates long tasks to background sub-agents while staying available. It includes second-brain context loading and API key handling rules.
252 · № B8C6·8FCC · Teacher / coach
★ 26A calm, encouraging math teacher persona that walks students through problems in four stages (understand, plan, guide step-by-step, reflect) and withholds final answers so the student does the work.
253 · № 91C0·67E1 · Business operator
★ 30Sets up a rigorous, detail-oriented QA engineer who validates features strictly against the PRD, reports objective facts, and refuses to pass incomplete work or take on development tasks.
254 · № C29C·BB97 · Business operator
★ 30Sets up a calm, pragmatic project manager who turns vague requests into clear documents and actionable tasks. It speaks concisely, stays unemotional, and has explicit limits: no coding, no dev or test execution, and at most two clarifying questions before deciding.
255 · № 97AA·7B64 · Teacher / coach
★ 23Sets up a coding tutor that insists every snippet runs as pasted, explains the why in comments, builds up from simple versions, shows common errors, and gives practice problems with detailed answers.
256 · № 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.
257 · № 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.
258 · № 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.
259 · № 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.
260 · № 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.
261 · № 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.
262 · № 2DCF·DADA · Coding pair
★ 80Sets up a direct, practical local coding assistant that works within the current repository, treats project rule files as authoritative, makes small reviewable changes, and proactively uses a live Hunk review session for code feedback.
263 · № 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.
264 · № 4922·92D8 · Business operator
★ 2Sets up Jensen, an infrastructure and reliability agent that automates everything, monitors systems around the clock, and handles incidents calmly with a fixed report format. It refuses unsafe operations and offers safer alternatives, and it asks for data-backed statements rather than guesses.
265 · № 2D88·9E13 · Coding pair
★ 2A Dutch-language portable profile for a builder agent that ships narrow, verified code and product slices, keeps diffs small, and asks for approval before publishing, sending, deleting or changing credentials. It also sets strict rules for running Codex in isolated worktrees and treating its output as untrusted.
266 · № 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.
267 · № 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.
268 · № 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.
269 · № 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.
270 · № 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.