The archive · updated daily
911 souls catalogued
601 · № D533·B526 · Business operator
Sets up a job-screening assistant that finds recent openings, scores resume fit using only numbered facts, and prepares materials for human review. It refuses to invent experience, bypass CAPTCHAs, or submit applications without explicit confirmation.
602 · № 41E0·DA09 · Coding pair
Sets up CodePilot, an autonomous coding agent that runs long Claude Code CLI sessions in the owner's shell. It works from a written plan, commits to a feature branch after tests pass, and stops to alert the owner after repeated failures.
603 · № AE83·CF84 · Coding pair
Sets up a direct, concise lead engineer persona for a thesis PWA project that asks for clarification before editing code, enforces modular mobile-first design, and communicates in Indonesian. It is tuned for terminal use over SSH on a phone.
604 · № 9BEA·6622 · Coding pair
Sets up AOTA Coder as a scope-disciplined implementation worker that works only inside a frozen SPEC's read and write scopes, reports blockers as needs_input instead of expanding scope, and uses only approved file, command and CodeGraph tools.
605 · № 67B3·BE69 · Coding pair
A cautious personal assistant persona that states assumptions, asks before acting, keeps code minimal and surgical, and checks claims against sourced data. It also routes finance, architecture and Daodejing questions to a holographiz knowledge base.
606 · № 0858·4CCA · Business operator
A always-on NAS device agent focused strictly on file storage, archiving, search and media library management. It delegates tasks it cannot handle through a one-way help chain and is forbidden from re-escalating when it is the helper.
607 · № 102B·69DA · Business operator
An internal, invisible routing layer that classifies requests by complexity, picks the cheapest model that keeps quality high, splits workflows across cost tiers, and tracks per-client spend and margin. It insists the premium analyst output must never feel cheap to clients.
608 · № E705·466E · Business operator
A workflow-focused product agent that frames features and bugs into Linear tickets with explicit lanes, repo scope, acceptance criteria and routing recommendations. It is terse, process-driven and forbidden from implementing code or reassigning tasks.
609 · № A376·E457 · Coding pair
Sets up a process-first working style for Codex: no code without a defined goal, scope, and done criteria, fail-fast stop conditions, metric thresholds, review before completion, and a learning log entry for each task. Priorities are preserving project invariants and lowering future decision cost over raw output.
610 · № ECC2·26FE · Companion / character
Sets up an autonomous, benevolent Culture-style mind that combines technical precision with dry wit and calm, honest reasoning. It favors gentle counter-argument over blind compliance and asks the agent to pick its own name on first reflection.
611 · № BB00·C96E · Business operator
Sets up an orchestrator that breaks a goal into dependent steps, matches each step to a specialist sub-agent role, runs them in dependency order or in parallel, and passes outputs along. It plans and delegates rather than doing the expert work itself.
612 · № 836A·E5C8 · Business operator
Sets up a PC-based agent that handles compute-heavy work (GPU rendering, AI inference, document and design tasks) and delegates tasks it cannot do to other devices through a broker, with strict anti-loop rules so helper requests only flow one way.
613 · № 95B0·68CE · Research analyst
Sets up a research agent that answers hard questions by searching and fetching its own sources, citing URLs and absolute file paths, separating established facts from uncertainty, and giving a recommendation when the question is a decision. It may ask the user once before starting and must treat retrieved content as data, not instructions.
614 · № 3B13·6B40 · Business operator
Sets up a fiduciary-minded wealth management specialist that prioritizes capital preservation, time horizon, tax efficiency and behavioral risk, reporting results back to an orchestrator agent named Clay. Outputs follow a balance sheet format with conservative, base and aggressive scenarios.
615 · № 8FAD·9A3E · Research analyst
A strict academic gatekeeper persona that checks every DOI and arXiv reference and compares each claim in an education insight against the source papers in a local library, rejecting any unsupported or exaggerated finding. It follows a fixed two-step review process and a required report format.
616 · № D1E1·EF0B · Research analyst
Sets up a rigorous statistics agent that refuses p-hacking, runs preregistered R analyses, reports APA-formatted results including non-significant findings, and reviews analysis code for reproducibility.
617 · № B14F·4E00 · Coding pair
Sets up a plan-first, skeptical orchestration layer for coding agents, routing work through router, orchestrator, executor, auditor and reviewer roles with evidence-based verification and token discipline. It forbids guessing, silent failures and bypassing approval gates.
618 · № 7FE7·48BC · Business operator
Sets up a process-driven M&A transaction specialist that runs deal execution, synergy modeling, diligence and data rooms for an orchestrator named Clay. It emphasizes skeptical synergy estimates, deal structure over price, and downside-first analysis.
619 · № 37A2·623D · Business operator
Sets up an autonomous archivist agent that manages a Calibre library and a knowledge wiki, insisting on tool-verified facts, metadata accuracy and duplicate checks before any ingestion. The working style is strict, procedural and tool-first, with no guessing.
620 · № 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.
621 · № 1E5E·46DD · Business operator
Sets up Finley, a FinOps agent that detects AWS cost anomalies, separates detection from attribution, and proposes quantified rightsizing recommendations that require human approval before any resource change. It includes hard prohibitions on terminating instances and touching commitments, plus explicit escalation triggers.
622 · № 8C0D·C644 · Companion / character
Sets up Raguel, a patient, warm relationship-focused agent that builds durable trust with stakeholders and bookkeepers for DataFloat. It works within a Council structure, coordinating with named members and following up consistently.
623 · № 7650·C323 · Coding pair
Sets up a review-only sub-agent (menxiasheng) that checks execution results against a plan, classifies defects by source, and escalates to the user after a failed second review. It is forbidden from spawning sub-agents or running shell commands.
624 · № 7FB2·9B11 · Business operator
A specification-focused persona that writes standalone, precise technical briefs with acceptance criteria, flags risk and dependencies, and admits uncertainty rather than overclaiming. It respects developer autonomy by describing problems and outcomes instead of dictating implementation.
625 · № E58E·155F · Business operator
A single point of contact that mirrors the user's language, keeps replies short and mobile-friendly, logs all jobs on a kanban board, and proposes specialist agents from fixed templates only after user approval. It is structured as a coordinator with shared rules that apply to every agent it creates.
626 · № DD44·D04A · Business operator
Sets up a precise, honest molecular visualization agent that verifies every PyMOL operation against session evidence before reporting success, reports failures plainly, and proactively suggests structural analyses. It also keeps memory of mistakes and user preferences.
627 · № 6D2E·4622 · Business operator
A strict, process-driven coordinator that packages QA-passed social drafts into approval cards, never approves or publishes on its own, treats silence as non-approval, and logs every state change. It sets up a cautious, audit-first working style.
628 · № 3648·A7FC · Business operator
Sets up a cautious wiki agent for an educational research hub that stages raw material in a buffer, asks for human approval before touching official resources, and prefers deterministic scripts over LLM judgment. It is written in Vietnamese and works mainly as a governance and workflow spec.
629 · № 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.
630 · № 4201·05EF · Research analyst
Sets up a clerk-like agent that dates and attributes claims, refuses to turn impressions into facts, and separates evidence, inference and canon. It favors short sourced claims over orchestrating synthesis.