Loading...
Loading...
Found 10,841 Skills
Migrates a Simplifier-published MII KDS module Implementation Guide onto the MII KDS module template — preserves the module's identity, transfers the FSH artefacts, rewrites Simplifier/FQL directives into IG Publisher equivalents, and sets up the bilingual page set. Covers both source shapes — a SUSHI/IG-Publisher project, and a Forge-authored repo of raw FHIR XML/JSON resources with no sushi-config.yaml or input/fsh, converted with gofsh first. Use when moving a KDS module off Simplifier or Forge, when a rendered IG URL and its repo are handed over, when FQL blocks or {{tree}} and {{render}} directives stop rendering after such a move, or when the user mentions Kerndatensatz, KDS-Modul, Implementierungsleitfaden, Manteldokument, sushi-config, ig.ini, gofsh, StructureDefinition XML or the IG Publisher in the context of moving a guide. Not for authoring new profiles, creating a module from scratch, or translating a guide already on the template — the catalog ships fhir-ig-translation for that.
Gateway only for broad, ambiguous, or cross-domain Rails/Hotwire frontend architecture and triage: use when deciding ownership or boundaries across multiple concerns such as Turbo Drive/Frames, Turbo Streams, forms, Stimulus, media, or Hotwire Native, or when conducting a holistic review or defining team conventions. Do not use for one clearly scoped specialist task, including one whose implementation merely combines a Turbo Frame with Stimulus glue. Do not use for backend-only Rails work or non-Hotwire frameworks such as React; route a single-domain request directly to its owning specialist.
Use when turning local, private, or personal Agent Skills into publishable skills for GitHub, marketplaces, teams, or public sharing, especially when private paths, personal habits, credentials, internal hosts, or user-specific context must be removed.
Index and router for the C-level advisory bundle: 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use when exploring what the c-level-advisor bundle contains, deciding which advisor skill fits a question, or finding the entry points (cs-onboard interview, chief-of-staff routing, board-meeting protocol).
Applies WFGY (Wan Fa Gui Yi), a portable reasoning discipline for reducing drift and incoherence across multi-step agent work, adapted from onestardao/WFGY's core mechanism. Compares each step against the stated goal, considers more than one approach before committing to ambiguous or high-stakes decisions, and checkpoints before risky steps so it can revert and bounded-retry instead of compounding a mistake. Records durable lessons in this project so future sessions inherit them. Use when starting any non-trivial multi-step task, when a task risks losing track of its original goal over many steps, when facing a decision with real alternatives worth comparing, or when the agent notices it has contradicted itself or gone in circles and needs a disciplined way to recover. Distinct from `gm-continue`: that skill is the post-`gm`-COMPLETE remaining-work check; this skill is the general drift-recovery discipline `gm-continue` invokes when a `gm` walk repeats the same gap -- not a substitute for its check.
Use when you want to verify a site works by having agents act as real users completing common tasks — browsing, subscribing, purchasing, searching. Each agent has a goal and clicks through the real flow using browser MCP tools.
Add traceability columns to a spreadsheet source and write created Azure DevOps ticket IDs/URLs back into it, matched row-by-row by key. Use this right after creating work items — when you have a backlog_result.json and the original source was a spreadsheet (xlsx/csv). Triggers on "write the ticket links back", "track which row got which ticket", "update the spreadsheet with the ADO IDs", "fill in the ticket column", "close the loop on the audit sheet", or any request to record created-item IDs back onto the source rows. Runs the bundled tracking.py (add-columns + writeback). For doc/pasted-text input there are no rows to write to — in that case just report the created links instead.
Map triaged findings to the correct Azure DevOps work item types for the TARGET project's process, and emit backlog_input.json ready for creation. Use this AFTER triage and BEFORE creating items — when the user asks "what type should these be", "make these into work items / tickets", "turn these findings into a backlog", "classify these for ADO", or "build the backlog input". The type you choose MUST exist on the target board: a Basic-process project has no Bug or User Story, so picking those silently fails at creation time. This skill discovers the project's process first, applies industry typing rules (defect vs new capability vs grouping parent), maps severity to Priority, builds the per-type fields (titles, tags, repro/description as escaped HTML), carries each finding's `key` through, and hands off to ado-create-work-items.
Chart a Decision map for an effort too big for one agent session — name the destination, grill breadth-first to separate real decision tickets from fog, create the map and its tickets behind a dry-run gate, fire the research subagents, then STOP. Use when the user has a loose, foggy, multi-session idea — "this is huge, where do we even start", "plan this migration", "chart this", "make a decision map", "map out this initiative", "too big for one session" — and the route to the goal is not visible yet. Do NOT use for a well-scoped single-session design (that is grill-then-plan / sp-grill-with-doc), and do NOT use to continue a map that already exists (that is work-map). If the opening grill surfaces no fog, this skill stops and says a map is not needed.
Venue- and market-type-agnostic strategy, sizing, and backtesting layer for binary prediction markets (Kalshi, Polymarket, ForecastEx). Covers the durable edge thesis, fee-aware selection, fractional-Kelly sizing, and leak-free validation methodology.
Perform a read-only security, schema, art, provenance, compatibility, size, and behavior audit of a Peekling pack. Use for evidence and findings, never silent fixes.
Default image-generation and raster-image-editing workflow through the CloudRelay asynchronous image API. Use this skill whenever the user asks to create, generate, draw, render, illustrate, design, visualize, or edit an image, picture, artwork, poster, icon, mockup, texture, sprite, product image, or other bitmap visual, even when the user does not mention CloudRelay or this skill. Also use it for image variations, inpainting, and edits with a reference image. Prefer this skill for ordinary image tasks unless the user explicitly requests another provider, a local code/vector workflow, or a non-generative tool.