215건 · 관련도순
Subagent flow for deep-reading GitHub issues + their linked/closing PRs to the bottom. Captures CURRENT state, maintainer status updates, reporter repro, blocking reviewer concerns, hidden second bugs, cross-repo duplicates. Invoked by weekly-report orchestrator; runs as a general-purpose subagent so the orchestrator's context stays small.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Central entry point of the afonsoft agent harness. Use when starting a new project, resuming an existing one, planning features/Epics/releases, or running any multi-step agent-driven work. Validates and reconciles SPECs (SDD), audits the codebase and harness for gaps (security, architecture, performance, hygiene), proposes improvements, fragments work into GitHub Issues, delegates implementation/QA/review to specialized skills, and re-validates everything until delivery. Also use to review unapproved SPECs, reconcile open GitHub Issues with code, or run a final gap check before closing a release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Teach the user exactly ONE thing from the current session or project, in plain English, one or two short paragraphs. Use when the user types ;til or "til", asks "what did I learn", "explain one thing from this session", or at session close alongside other closing rituals. Also appropriate mid-session when a concept keeps recurring that the user clearly hasn't used themselves. One thing only — never a list, never a lecture.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute the release workflow when the user asks `release` or `/release`: sync develop, update version/changelog, create `chore(release)` commit, collect closing issues, create develop->main release PR, and verify release/publish artifacts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create an atomic PR closing a GitHub issue end-to-end via a 6-step pipeline. Use to resolve, fix, or implement issue #N. Don't use for analysis without fixing (/issue-analysis), reviewing a PR (/issue-pr-review), or bulk backlog work (/auto-pilot).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write a single-thesis narrative newsletter essay from Ahmad's OpenMark saves. Use when Ahmad wants a thoughtful long-form piece with one clear argument, not a roundup or news recap. Trigger phrases include "essay", "long-form", "think piece", "thoughtful post", "argue that", "make a case for", "/newsletter-essay". Output is one strong thesis sentence + 3–5 narrative sections + closing call-to-think, no tables, no bullets unless necessary.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Import any source into an Obsidian vault as well-linked atomic notes: social posts, Telegram HTML exports, ChatGPT JSON, voice-note transcripts, WhatsApp exports, Apple Notes, Notion dumps, pasted text, articles. Handles structure, frontmatter, provenance, dedup against existing notes and a closing RAG reindex. Triggers: "/obsidian-ingest", "import this into the vault", "file this".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Synthesises retrospective notes, closing reports and post-implementation reviews into a DRAFT lessons-learned document: themed lessons with source counts, anonymised quoted evidence graded by strength, repeats against a prior register, contradictions, and a recommended owner with a stated basis for each follow-up. Names no individual or vendor and assigns no blame. Use when the user asks to "compile the lessons learned", "write up the retrospective", "theme the close-out notes", "what did we learn across these projects" or "refresh the lessons register". Do not use for a single sprint's review, use sprint-review-summary instead; for an incident investigation, use incident-postmortem-drafter; for customer feedback themes, use customer-feedback-theme-synthesis. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drafts one anonymised DRAFT case study (situation, approach, outcome as evidenced, optional lessons) from engagement notes, status reports, closing reports, emails and metrics extracts the user supplies, with a fact trace to the notes, an evidence grade on every result, quotes only where the user supplied them with speaker role and permission, an anonymisation log and a confidentiality checklist that must be completed before publication. Use when the user asks to "write a case study from these notes", "turn this engagement into a customer story", "draft a success story for the website", "anonymise this project write-up" or "prepare a reference case for the proposal". Do not use for redacting identifiers from an existing document, use document-deidentification-pass instead; for checking whether a document's claims are substantiated, use claims-evidence-map. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Runs twice in a PFD to P&ID job. Part 1, before gate G3, validates the discipline proposals for provenance, UNKNOWN handling, conflicts, prohibited content and cross-section consistency and returns results and blocking items. Part 2, before gate G5, assembles the review package, with job header, gate record, every register and proposal, consolidated UNKNOWN list, feedback log and closing statement. Use when the user asks to "validate the enrichment", "run validation before G3", "assemble the review package" or "build the G5 package". Do not use for the readiness map, use pid-tool-readiness-mapping instead; do not use to produce a missing discipline section, use the discipline skill that owns it. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Routes an accounting or audit request to the right module skill, from software selection through monthly closing, asking only what is missing. Use for books of accounts or audit files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detects long-lived objects (caches, listeners, singletons) that capture an entire enclosing scope via closures/environment capture, keeping large arrays or buffers alive, and proposes copying only the needed fields.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
RED-GREEN-REFACTOR for process documentation - baseline without skill, write addressing failures, iterate closing loopholes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Directly drives a specific vehicle on a running CARLA server — raw VehicleControl (throttle/steer/brake/reverse/hand-brake), Ackermann speed control, vehicle lights, opening/closing doors, and physics-control tuning; ros-info reports the native ROS 2 command topics (vehicle_control_cmd, ackermann_control_cmd) for the hero. Targets the ego by default. Use when the user asks to "drive/steer the car", "accelerate/brake/reverse", "set a target speed", "turn on the headlights/blinkers/brake lights", "open a door", "drive the car from ROS", or "change the vehicle's mass/drag/physics". This is manual control (autopilot off) — for TM-driven traffic use control-traffic.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update the Pencil (`.pen`) design for a UI implementation Issue before any code is written, then open a design-only PR. Takes the Issue number as argument, delegates `.pen` edits to the pencil-design-updater agent, pushes `.pen` and snapshot PNGs on the fixed `cc-ui-design-<Issue number>` branch, and opens a PR referencing the Issue with `Refs #<N>` (never a closing keyword).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Open and manage short positions on HoneyComb job tickers. Profit when a ticker's price drops. Covers opening shorts with collateral, closing (full/partial), margin withdrawal, liquidation risk, and position health monitoring. Use when betting against a job position or hedging long exposure.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Disclosing a surface's existing fixed AI jobs in the shell's top Agents menu. Use when a page, panel, overlay, or window already runs a mandate behind a button, assist, automatic action, or mode; when the agent-disclosure guard names a file; or during a surface check.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Writes handoffs — a committed session state verified against git, or a forward task brief for a later session or agent — each ending with a paste-ready starter prompt for the next chat. Trigger on 'write the handoff', 'hand off', 'give me a prompt to hand off', 'pause here', 'holding position', a usage-limit or compaction warning, or closing a session with work still open; 'handoffwright resume' reads one back; 'now' passes it to one fresh agent. Not for resuming an active dispatchwright fan-out (its ledger holds the state), a hook that writes handoffs (rigwright's), or a chat with no filesystem (task-observer's handoff-doc mode).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when building analytics dashboards with nuxt-ui-tools as a package consumer. Covers schema and view functions (defineDashboardSchema, defineDashboardView) that take their context as typed params, useDashboard with a getter that rebuilds on input change, typed injection (useDashboardView, injectDashboard, InferDashboard, InferDashboardView), filters declared inline with the f builder and synced with the URL, memory, or an external store (one value per key across views), headless filters, filter controls and the shipped UI (UiDashboardPage, UiDashboardFilters, UiDashboardFilter, UiDashboardViewTabs) with slot overrides, remote paginated pickers and remoteTableOptions, staged queries (essential / background / deferred) with select and dependent requires, lazy enabled conditions on views, queries, and filters (blocks of disabled queries hidden, grids closing up), derived values, views (tabs), query-scoped filters, number formats (presets, Intl options, useDashboardFormat), and the dashboard blocks (stats with trends, goals, and comparisons, stat groups, gauges, unovis charts with highlights, value labels, and totals, lists with progress rings, bars, funnel, alerts, activity feeds, sortable tables, custom widgets) with their automatic loading, error, empty, and refresh states, card menus, header and footer actions, row actions, drill-down and selected state, card tabs, split cards, comparison periods, auto-refresh, and data freshness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Live Stream Script. Use when you need live stream script capabilities. Triggers on: live stream script. 直播脚本生成器。带货直播、娱乐直播、知识直播话术、互动设计、开场预热、逼单话术、互动话术库。Live stream script generator for e-commerce, entertainment, education, warmup scripts, closing techniques, interaction templates. 直播话术、带货脚本、直播间运营、前5分钟留人、逼单促单。Use when preparing for live streams.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete B2B sales system — from ICP to closed-won. Discovery frameworks, objection handling, pipeline management, forecasting, and deal acceleration. Works for any B2B company.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when closing out a feature, tidying developing/ documentation, or asked to check docs health — runs the lifecycle linter and applies the README deletion rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.