Coordinating subagents: whether and how widely to delegate, briefs with boundaries and hand-back schemas, partitioned writes with an idempotent merge, verifying what a subagent claims, fair comparisons, and fan-out scripts with caps and resume.
Plugin agent-orchestration from marketplace modootoday in modootoday/marketplace. Commands read from the repo's manifest — 23 days ago.
delegation-decision-and-sizingDecide whether a task goes to zero, one or several subagents and how many - classify it as wide read-only, write-coupled or sequential, keep small or sequential work in one agent and say why, size a fan-out by breadth with a stated token multiple, pick the mechanism (turn-by-turn helpers, a script,
eval-comparison-hygieneKeep a with-versus-without measurement honest when the change is a skill, prompt or agent and the graders are models - hold subject model, judge, grader text, prompt and environment constant across both arms run in the same batch, invalidate old baselines after any grader or prompt edit, keep refere
fan-out-script-designDesign a script that drives dozens or more agents - phases of discover, per-item pipeline, independent verification and one reduce step, barriers only where a stage needs every result, a deterministic script with no clock or randomness and per-item prompts independent of siblings so a resume reruns
parallel-write-partitioning-and-mergePlan several agents that write to the same repository or store - list every path and shared record, give each to exactly one agent, isolate writers in separate copies while naming what isolation does not cover (ports, databases, caches, the shared index), have workers write per-agent pending files,
subagent-brief-and-handbackWrite the prompt for a subagent so it can succeed alone - one-sentence objective and done-state, the context it cannot see, the exact write set it owns and what it must not touch, a value contract for every output field, a stop rule with a budget, forbidden shortcuts with an explicit blocked exit, a
subagent-claim-verificationUse when the user pastes a subagent's or worker's report claiming results (all tests pass, 5 of 5 cases at 1.00, fixed, only touched one file) together with its output, and asks you to draft the announcement, say whether it is safe to accept, merge or ship, or verify it first. Do not take the report
Your own Naver blog, Place, Smart Store, shopping, search ad and news comment data read through the datalab.tools browser extension, plus card news, short-form video, tutorial posts and social copy built in its editors, with no invented numbers and no change made without asking.
31 skills
Numbers that mean what they say: ClickHouse SQL that reads the key and deduplicates correctly, Naver trend data read as ratios, metrics defined once, experiments designed before launch, retention read by cohort, and open survey responses grouped with every response id kept.
16 skills
Reading passages that hit a measured grade level, language drills, and teacher-side checks for coverage, answer keys, lesson timing, study calendars and rule-valid puzzles, with the numbers and logs shown.
14 skills
Growth and community work: store listings written for the people searching that store, Discord servers run with structure and consistent moderation, newsletters readers open and finish, a month of social posts a small team can ship, launch emails that lead with what changed, and sites submitted to Google, Naver and IndexNow engines from a pipeline.
13 skills
Early product-planning steps done carefully: spar on an idea, frame the problem behind a request, synthesize feedback without overstating it, rank a backlog while saying where the ranking is fragile, write a Korean PRD with testable acceptance criteria, and put a decision on one page with the recommendation first.
13 skills
Korean content that reads well and stays true: product copy fixed to the Toss writing principles, Naver blog posts planned for search, persona tone measured with markers, and ghostwriting that never invents the author's facts.
11 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.