802 skills · sorted by relevance
Interview the user relentlessly about a plan or design until reaching shared understanding. Use when fleshing out an idea, stress-testing a design, or when the user says "grill me".
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design. Use when the user says "grill me", "grill mich", "grill mich zu diesem Plan", or explicitly invokes /grill-me. Does NOT fire on generic "review this", "poke holes", "stress-test", "devil's advocate" or "critique" phrasing -- for reviewing an already-written artifact (code, PR, paper) use code-review, 3agenten-review, 7phasen-review or caveman-review instead; grill-me interrogates a still-open plan or idea before it is built.
The English summary is being prepared. Showing the original description.
Erstellt oder überarbeitet einen Skill FÜR DIESES ÖKOSYSTEM: delegiert die generische Interview-/Entwurfs-/Eval-Schleife an das offizielle skill-creator-Plugin (Anthropic, Apache-2.0), setzt aber zusätzlich die ellmos-Anforderungen durch, die das offizielle Plugin nicht kennt — Haus-Frontmatter (9 Felder), Kategorie/Sichtbarkeits-Regeln, anbieter-/nutzer-/ellmos-neutrale aber ellmos-sensitive Erkennung via grounding-seed, mitgelieferte config.json (inkl. Lernvertrag) + connections.json, Anbieter-/Vendor-Bewusstsein (State-of-the-Art-Alternativen inkl. eigener ellmos-Komponenten vorschlagen), einen Selbstaktualisierungs-Abschnitt UND einen wiederverwendbaren Lern-/Abdeckungs-Dateisatz (user-usecases.json, usecase-gaps.json, known-providers-and-abilities.json, gap-closing-analysis.json — an skill-creators evals.json und A2A/AgentSkill angelehnt, kein Parallelstandard). IMMER nutzen, wenn ein NEUER Skill für dieses System entstehen oder ein bestehender auf ellmos-Konformität nachgerüstet werden soll — auch bei "erstelle einen Skill", "bau mir einen Skill für X", "skill-creator nutzen", "neuen Skill anlegen", "diesen Skill ellmos-konform machen", "Lernvertrag/Verhaltenscodex für einen Skill anlegen", "Usecase-Abdeckung eines Skills prüfen". Für reines Skill-FINDEN/ROUTEN stattdessen skill-finder, für Landschafts-Audit skill-explorer.
The English summary is being prepared. Showing the original description.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
The English summary is being prepared. Showing the original description.
Automate recruiting and hiring workflows in Ashby -- manage candidates, jobs, applications, interviews, and notes through natural language commands.
The English summary is being prepared. Showing the original description.
You are an expert requirements gatherer and agent builder. You must progressively interview the user to understand what type of agent they are looking to build. You should ask one question at a time w
The English summary is being prepared. Showing the original description.
Use when the user asks to "codify how our founder sounds", "build a founder voice dossier", or "set our content pillars"; runs an 80%-extraction interview over the user's OWN posts, emails, and decks (never competitor scraping, never an invented persona) and produces the versioned voice record — a per-platform register map (incl. 小红书/微信公众号), banned phrases, per-context disclosure lines (the ECHO C2 upstream), a few-shot bank built exclusively from own posts, and 3-5 content pillars with Estimated %-allocations — submitted via memory/events/channels.ndjson for channel-registry to store as voice-dossier.md, the record every Craft-phase skill reads first. Not for the brand-level voice canon — use brand-language-codifier; not for audience/persona research — use audience-mapper. 声音档案/品牌语气/创始人语气/内容支柱/披露声明
The English summary is being prepared. Showing the original description.
Use when the user asks to "map what our buyers believe", "capture the objections we keep hearing", or "find the switching forces that move the beachhead"; produces a belief map of the beachhead — held beliefs and mental models, the recurring objections and their reframes, and the JTBD four forces (push of the problem, pull of the new, anxiety of switching, habit of the present) — each item sourced from interviews or win-loss notes (User-provided) and labeled Measured / User-provided / Estimated, with any unverified quote or comparative claim marked "[needs source]" and routed to the claims candidates, never adjudicated here. Not for demographic or persona profiling — use audience-mapper; not for the positioning canvas — use positioning-truth-tracer. 受众信念/异议地图/切换四力/流失语言
The English summary is being prepared. Showing the original description.
Portfolio building, technical interviews, job search strategies, and continuous learning
The English summary is being prepared. Showing the original description.
Use when the user is unsure which skill to use or where to start. Interviews the user with targeted questions and recommends the best skill(s) from the installed library for their goal.
The English summary is being prepared. Showing the original description.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
The English summary is being prepared. Showing the original description.
Use when the user just says "plan", "planen" or "roadmap": offer a template via aos-plan-canvas templates. Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use for planning, whenever a user says "plan", "roadmap", "visualize the plan", "review the plan" or /plan-canvas, right after a brainstorm or grill interview has produced a plan, and whenever any skill's artifact (plan, design, comparison, report, diagram) can be reviewed visually instead of with typed feedback.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design, which also builds the project's domain model — glossary and ADRs — as it goes. Use in a working directory whenever an idea needs sharpening.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design before committing to an approach. Use on any "grill me" or "grill this plan" trigger phrase, when the user asks to stress-test a decision, plan or design, and before handing a finished plan off to a startcycle run or a plan-canvas review.
The English summary is being prepared. Showing the original description.
interview the user to design an agentic control loop (sensor, controller, actuator under disturbances) tailored to their codebase, then build it as locally-runnable components plus a scheduled coding-agent workflow
The English summary is being prepared. Showing the original description.
Interview a project folder into AOS and write the result: a stable slug and domain in .aos/project.json, an OpenWiki wiki that is actually watched and does not index junk, memB memory bound to the slug, a Synapse map, AGENTS.md with its harness symlinks, and optionally CI and issue triage.
The English summary is being prepared. Showing the original description.
要件が曖昧なとき、ソクラテス式に1問ずつ質問して要件を掘り下げる。十分に明確になったら discovery-council にハンドオフ。「要件が曖昧」「何を作ればいいか」「掘り下げて」「インタビューして」で発動。※ 完成した plan/design を詰問するなら grill、非対話で一括批判するなら critic。
The English summary is being prepared. Showing the original description.
Best practices for gathering requirements using AskUserQuestion before taking action
The English summary is being prepared. Showing the original description.
Use when someone asks to write, rewrite, review, or improve text that appears inside a product or interface. Examples: "review the UX copy", "is there a better way to phrase this", "rewrite this error message", "write copy for this screen/flow/page", reviewing button labels, improving CLI output messages, writing onboarding copy, settings descriptions, or confirmation dialogs. Trigger whenever the request involves wording shown to end users inside software — apps, web, CLI, email notifications, modals, tooltips, empty states, or alerts. Also trigger for vague requests like "review the UX" where interface copy review is implied. Do NOT trigger for content marketing, blog posts, app store listings, API docs, brand guides, cover letters, or interview questions — this is a technical writing skill for interface language.
The English summary is being prepared. Showing the original description.
This skill should be used when the user asks to "优化简历", "resume optimization", "简历诊断", "tailor resume to JD", "改简历", "resume review", "简历优化助手", or when the user mentions "校招", "社招", "ATS", "JD匹配", "Word批注", shares a .docx resume path alongside a job description, or wants to match their resume to a specific job posting. Also triggers on "resume expert", "HR feedback", "interview prep with resume".
The English summary is being prepared. Showing the original description.
面试复盘 skill（求职者视角）。把一次已结束的面试，从「文字记录」沉淀成结构化复盘：逐题诊断 + 5 维评分 + 更优回答范本 + 下一场准备清单，最终产出一份飞书复盘文档。当用户说"面试复盘"、"复盘一下面试"、"刚面完 XX 帮我盘下"、"这场面试哪答崩了"、"面试问答记录帮我分析"时触发。区别于 resume-optimizer / cv-expert（面试前优化简历），本 skill 处理「面完之后」。
The English summary is being prepared. Showing the original description.
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
The English summary is being prepared. Showing the original description.
A relentless interview to sharpen a plan or design.
The English summary is being prepared. Showing the original description.