5,822 件 ・ 関連度順
概要と使いどころ
Create a bookkeeping context profile before downstream bookkeeping work. Captures entity type, tax jurisdiction, accounting method, chart of accounts baseline, connected tools, approval thresholds, record-retention policy, and review boundaries. Trigger on "set up my bookkeeping", "bookkeeping context", "chart of accounts", "cash or accrual", "configure my books", "what info do you need before bookkeeping".
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
日本語の概要は準備中です。原文の説明を表示しています。
Run an always-on Telegram watch loop under a separate assistant account using MCP push tools. Mode 1 answers when the assistant account is mentioned in team chats, with actionable vault-grounded advice; mode 2 ambiently watches designated chats and pings on salient events. Triggers: "/telegram-watch", "start the telegram watch".
日本語の概要は準備中です。原文の説明を表示しています。
- Research companies, directors, shareholders and ultimate beneficial ownership in official corporate registries, filings and offshore datasets — OpenCorporates, UK Companies House and the PSC register, SEC EDGAR, US Secretary of State registries, EU business registers, GLEIF LEI… Use when asked who owns or controls a company, to find a person's other directorships, or to unpick a group structure
日本語の概要は準備中です。原文の説明を表示しています。
Finds high-value SEO and GEO keywords using web search, AI analysis, and optionally paid tools like Ahrefs or Semrush. Produces a validated keywords.csv file with a fixed schema for downstream pipeline consumption.
日本語の概要は準備中です。原文の説明を表示しています。
Operating manual for Telegram over its MCP connector and roughly 115 tools: how to find a chat by title, the tool inventory grouped by job, resolving chat ids, auto-transcribing voice notes, and the connector gotchas (pinned-first ordering, big-page crashes, reload after reconnect, untrusted fields, always passing an explicit account). Load before any non-trivial Telegram work.
日本語の概要は準備中です。原文の説明を表示しています。
Build a dossier on a person: recall everything the vault already knows, map their public profiles by web research, emit a deep-research prompt for external tools, and persist a well-linked person card. Triggers: "/portret <name>", "dossier on <name>", "profile <name>".
日本語の概要は準備中です。原文の説明を表示しています。
Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".
日本語の概要は準備中です。原文の説明を表示しています。
Senior engineer CLI expertise for AI agents — workflows, safety guardrails, gotchas, and anti-patterns across cloud, IaC, containers, databases, dev tools, and platforms
日本語の概要は準備中です。原文の説明を表示しています。
Route a task through SIPS commands, agents, scripts, MCP tools, or bounded delegation. Use when asked to route, split, fan out, escalate, or choose the right SIPS path.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Continuous production path for deployless repositories. Use after mainline governance and release controls exist, when a repo needs CI/CD changes to automatically deploy, publish, or promote artifacts from main across any language, runtime, or hosting platform.
日本語の概要は準備中です。原文の説明を表示しています。
Operational safety for deployless repositories. Use after mainline deployment and runtime release controls are designed, when a repo needs traces, replay tests, observability, rollback drills, smoke checks, compatibility windows, or expand-contract migration safety.
日本語の概要は準備中です。原文の説明を表示しています。
Use for release-level accessibility and performance review, including WCAG 2.2 AA, keyboard/focus, target size, reduced motion, semantic controls, Core Web Vitals, images/fonts/JavaScript, and animation or 3D performance budgets.
日本語の概要は準備中です。原文の説明を表示しています。
Read and modify MIKE+ model parameters via the mike-plus MCP server — inspect or change values in any model table (pipe Diameter/Manning in msm_Link, node levels in msm_Node, catchment properties in msm_Catchment, etc.). Use when an agent must identify a current parameter and change it before re-running. Requires MIKE+ + license; mutating tools must run on a copy.
日本語の概要は準備中です。原文の説明を表示しています。
Implements and reviews mobile data privacy across Flutter, Android, iOS, React Native and Kotlin Multiplatform. Use for consent withdrawal, SDK collection controls, account and data deletion, retention, privacy manifests or store data disclosures. Covers the app and backend handoff; security exploits belong to mobile-security.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the ArtCraft MCP integration — the community Python rebuild (C:\Users\rasta\artcraft-mcp-py\artcraft_mcp_server.py) that replaces the broken upstream artcraft-mcp.exe, the live api.storyteller.ai/v1 API map (required headers, cookie auth, endpoint schemas), the upstream bug/PR trail (issues #1/#3, PR #2), the reverse-engineering playbook (browser capture, cookie injection, schema fishing via validation errors, handshake replay, Windows MITM kit), and the generic MCP-protocol debugging playbook (snake_case servers, the shim pattern, 'missing field protocolVersion' diagnosis). Use when working on ArtCraft MCP tools, debugging an artcraft server connection, extending the Python rebuild, or diagnosing any third-party MCP handshake failure.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
日本語の概要は準備中です。原文の説明を表示しています。
**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) - Debugging MCP server issues or errors - Reviewing MCP server code for quality, security, or performance - Answering questions about MCP development or mcp-use patterns - Making ANY changes to server.tool(), server.resource(), server.prompt(), or widgets This skill contains critical architecture decisions, security patterns, and common pitfalls. Always consult the relevant reference files BEFORE implementing MCP features.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS assistant export/import track — the canonical nvoos-assistant bundle format (v1), the shared portability engine, its five surfaces (WP-CLI, REST, admin UI, AI tools, backup provider), the Pro blueprint exporter, credential-redaction rules, legacy/blueprint import compatibility, test conventions, and the Content Graph port checklist. Use when extending or debugging assistant export/import, adding a surface, changing the bundle schema, fixing round-trip fidelity, or continuing the portability track ("continue the portability plan", "add assistant export to X").
日本語の概要は準備中です。原文の説明を表示しています。
Provision a client-brand AI assistant in the NV oOS Pro Toolkit — brand intake, system-prompt authoring, tool selection, an idempotent provisioning script, credentials, and end-to-end verification. Use when creating a brand manager or social media assistant for a client brand (e.g. Aerlinn), onboarding a new brand into the Design Stack, replicating an existing brand assistant, or updating a brand assistant's prompt, tools, or campaign copy.
日本語の概要は準備中です。原文の説明を表示しています。
Register WordPress Abilities: machine-readable plugin operations with JSON Schema contracts, required permission callbacks, optional REST exposure, and AI/MCP-friendly discovery. Covers categories, wp_register_ability, WP_Ability::execute, REST run endpoints, meta.show_in_rest, annotations, and Ability vs REST route vs custom hook decisions. Use when exposing plugin functionality to agents, admin JS, external tools, or reviewing AI integration code.
日本語の概要は準備中です。原文の説明を表示しています。
Research, draft, and publish WordPress content — blog posts, product copy, SEO metadata, and media with accessible alt text — using NV oOS research and content tools.
日本語の概要は準備中です。原文の説明を表示しています。
Operating NV oOS WordPress sites through scoped MCP operator credentials — tool groups, task recipes, and site disambiguation. Use when working with NV oOS tools (create_post, woo_products, toolkit_cpt, paper_store, jetengine) on any managed site.
日本語の概要は準備中です。原文の説明を表示しています。