3,193 件 ・ 関連度順
概要と使いどころ
Pick one open GitHub issue off this repository's queue, implement the fix, and open a pull request for it. One issue and one PR per run. Use when the user asks to burn down the issue backlog, or when the issue-burndown workflow invokes it. It never merges, never closes an issue, never edits .github/workflows/, and never acts on an issue from outside the organisation unless a maintainer has opted it in.
日本語の概要は準備中です。原文の説明を表示しています。
Apply a set of Rosetta Stone attribute mappings to a Narrative dataset by wrapping them in a one-shot workflow that calls the `CreateRosettaStoneMappingsIfNotExist` task. Consumes the structured output of `/generate-rosetta-stone-mappings`, normalizes the generator's snake_case to the workflow task's camelCase, re-validates every expression against the dataset's current schema, gates on user approval, submits via `narrative_workflows_create`, polls the triggered run, and reports per-mapping created / conflict / failed. Use when: "apply these mappings to dataset N", "create the Rosetta Stone mappings I just generated", "push the mappings I saved earlier to <dataset>", "productionize this mapping list", "submit the suggested_mappings array". (narrative-common)
日本語の概要は準備中です。原文の説明を表示しています。
Author and submit a Narrative workflow from a natural-language intent. Picks the closest example from `assets/examples/`, adapts it to the user's case, walks the YAML against the spec, resolves the data plane, and submits via `narrative_workflows_create` only after the user has approved the rendered spec. Use when: "create a workflow that does X", "schedule a daily refresh of dataset Y", "wrap this NQL as a workflow", "build a pipeline that creates view A then refreshes view B", "submit this workflow YAML", "productionize this query as a recurring job". (narrative-common)
日本語の概要は準備中です。原文の説明を表示しています。
Create a look-alike audience from a seed audience and a candidate population dataset. Classifies Rosetta Stone attributes, generates the same materialized-view scoring pipeline Lookalike Studio emits (Naive-Bayes categorical weights + Gaussian continuous similarity), gates on approval, submits via `narrative_workflows_create`, and monitors the build to completion. Use when: "create a lookalike audience", "find more users like this segment", "expand my seed audience to 500k similar users", "score the population against my customers", "build a look-alike of dataset X". (narrative-audience)
日本語の概要は準備中です。原文の説明を表示しています。
Playwright workflows for deterministic third-party responses using page.route().
日本語の概要は準備中です。原文の説明を表示しています。
Diagnostic Playwright workflows for flaky or failing tests, including trace analysis, UI mode, and state isolation.
日本語の概要は準備中です。原文の説明を表示しています。
Playwright workflows for authenticated browser state reuse through storageState and setup projects.
日本語の概要は準備中です。原文の説明を表示しています。
Load when configuring GitBook documentation sites, authoring GitBook-flavored markdown pages and custom blocks, integrating OpenAPI/Swagger specs, driving GitBook Change Request workflows (create, review, comment, resolve), or building GitBook platform integrations. Do not use for general repository code reviews, general .NET OpenAPI schema generation, or non-GitBook markdown.
日本語の概要は準備中です。原文の説明を表示しています。
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Meta-skill for complete Roblox game development with Rojo — the entry point that knows and unifies the three specialist skills `/rojo` (filesystem→Studio sync, project setup), `/rbx-studio` (editor, MCP, assets, malware scan) and `/game-design` (roles, workflows, GDD). Use this skill for ANY Roblox game-dev undertaking: planning/building/setting up a Roblox game, scaffolding a new project, defining code architecture (Main + manager modules, _G.ClientState + HUD, remotes in GameEnums), avoiding Luau/Roblox pitfalls, or when it is unclear which of the Roblox specialist skills fits — routing happens from here. Also trigger on "develop Roblox game", "build Roblox game", "new Roblox project", "Luau project structure", "how do I organize Roblox code", "Roblox dev setup".
日本語の概要は準備中です。原文の説明を表示しています。
How game development works as a process — roles, subtasks, workflows and role descriptions, especially (but not only) for Roblox. Use this skill when it's about the ORGANIZATION of game dev rather than concrete code: Which roles exist (Creative Director, Engineer, Artist, Polish/Audio, Business, QA-Tester, Game Critic)? Who does which subtask? What does a development chain (concept → backend → frontend → polish → test) look like? How do you write a Game Design Document / KONZEPT.md? How do several (AI) agents divide up a game? Also trigger on "plan a new game", "create Game Design Document", "which roles do I need for my game", "development workflow for a game", "who tests the game", "structure a game idea", "Roblox genre/monetization".
日本語の概要は準備中です。原文の説明を表示しています。
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine Automatisierung", „das soll regelmäßig/nächtlich laufen", „extrahiere Workflows aus diesen Chatverläufen/Automationen", „Automation aus dieser Session bauen", oder bei `/workflow-extract`. Ergänzt fehlende Automations-Bausteine (Rotations-Auswahl, Check-Registry, Idempotenz, Log-Hygiene, Freigabe-Gate, Eskalations-Handoff, Monitor-Meldedisziplin) systematisch. Enthält auch den Fleet-Audit-Modus: bestehende Automations-Flotten auf Silent-Failures, Redundanz, Drift und Lücken prüfen („prüfe meine Automatisierungen/Scheduled Tasks/Cron-Jobs"). Soll stattdessen ein abrufbarer Skill (Fähigkeit auf Zuruf) entstehen, den Schwester-Skill skill-extractor nutzen.
日本語の概要は準備中です。原文の説明を表示しています。
Mouse, keyboard, and scroll primitives for cua_click / cua_type / cua_key / cua_scroll. Reference for action shapes, modifier keys, key chord syntax, and screenshot-driven targeting workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Manage n8n workflow automation via its public REST API — list/get/create/update workflows, activate/deactivate, inspect execution history, retry/stop executions, manage credentials, tags, variables, users, and projects. Works with self-hosted n8n and n8n Cloud. Use when the user wants programmatic access to their n8n instance without the n8n MCP installed.
日本語の概要は準備中です。原文の説明を表示しています。
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Health-check, audit and, on approval, fix a self-hosted n8n automation stack. Health is read-only; any workflow edit goes preview, approval, apply. Triggers: "/n8n", "/n8n health", "/n8n fix <id>", "which workflows are failing".
日本語の概要は準備中です。原文の説明を表示しています。
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms
日本語の概要は準備中です。原文の説明を表示しています。
Deployless delivery-model audit. Use first when adapting any repository toward single-mainline development, automatic deployment from main, runtime release controls, production-trace-driven iteration, AI PR governance, or multi-agent delivery workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Remote-sensing literature search, citation verification, sensor/platform/dataset query strategy, citation file management (.ris/.bib/.enw conversion), and reference management (BibTeX, related articles, DOI/arXiv lookup) across CrossRef, arXiv, Scopus, ScienceDirect, Semantic Scholar, and domain web sources. Use when the user needs coordinated multi-step literature workflows for remote sensing, Earth observation, geospatial AI, GIScience, photogrammetry, SAR, hyperspectral imaging, LiDAR, satellite missions, benchmark datasets, land-cover mapping, change detection, object detection, segmentation, retrieval, or multimodal remote-sensing foundation models. Also trigger on general literature-search needs during academic writing even without the word "Nature", such as searching for papers/literature, doing a literature review, verifying a citation, converting citation files, and Chinese phrasings like 文献检索、查文献、找文献、 文献综述检索、查论文、引文核对、参考文献管理、文献去重.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect and operate a WordPress site running NV oOS — site health, logs, users, media, and content queries. Read-first workflows for site operators and support staff.
日本語の概要は準備中です。原文の説明を表示しています。
Google Workspace cross-service productivity workflows via the gws CLI. Combines Drive, Gmail, Calendar, Sheets, Tasks, Docs, and Chat into multi-step automations.
日本語の概要は準備中です。原文の説明を表示しています。
Manage service components and approval workflows in the NV oOS Pro Toolkit. Covers service component registration, dependency tracking, approval request lifecycle, and workflow approval gates. Use when registering service components, tracking service dependencies, managing approval requests, or configuring workflow approval nodes.
日本語の概要は準備中です。原文の説明を表示しています。
Publish and schedule content to social media platforms (Twitter/X, Facebook, Instagram, LinkedIn) via the MCP bridge schedule_social_post tool as primary. The Design Stack media worker API is the fallback for advanced platform management. Covers platform-specific formatting, media attachment, scheduling, and WordPress-to-social publishing workflows. Use when posting to social platforms, scheduling future posts, attaching media to posts, checking optimal timing, or debugging API delivery failures.
日本語の概要は準備中です。原文の説明を表示しています。
Manage NV oOS Pro Schedules — create, update, delete, list, dry-run, view run history, and plan schedules from workflows. Covers all 7 Pro Schedule Manager MCP tools with usage patterns, cross-references, and operational troubleshooting. Use when creating recurring tasks, debugging schedule failures, pausing vs deleting schedules, converting Action Scheduler jobs to managed schedules, or bridging workflow outputs to timed execution.
日本語の概要は準備中です。原文の説明を表示しています。