4,001 件 ・ 関連度順
概要と使いどころ
Report what is genuinely new in the last 30 days on a topic, by slicing locally collected nightly channel databases with no live crawling. Run it before a strategic decision, as the fresh-signal feed for the gap phase. Triggers: "/last30days <topic>", "trendwatch <topic>", "what changed last 30 days on X".
日本語の概要は準備中です。原文の説明を表示しています。
List incoming deliverables held in quarantine: fixes, scripts and tasks that arrived over file sync from an unverified source or without a signature and are not applied until the owner decides. Fail-closed by design. Triggers: "/quarantine", "what is quarantined", or a deploy check reporting held items.
日本語の概要は準備中です。原文の説明を表示しています。
Recover a fleet whose machines cannot see each other over the file-sync network: establish ground truth at the hub from the live sync API rather than memory or one peer's claim, publish the hub's verified device id over the messaging rail, and walk each disconnected peer through re-pairing. Triggers: "/raise-sync", "sync is down", "machines cannot see each other".
日本語の概要は準備中です。原文の説明を表示しています。
Measure a target repository's queue and find a live open issue the contribution would close, before opening a pull request there. Reports how many PRs are open, how many of the last N closed ones were actually merged, and which issue to attach to, because a cold PR into a dead queue is a wasted artifact. Triggers: "/issue-match", "is this repo worth a PR", "measure the queue".
日本語の概要は準備中です。原文の説明を表示しています。
Load the operations codex that governs everyone acting as or for the owner (the owner, human assistants and AI agents) before outreach, replies in their chats, scheduling, purchases, hiring or household ops. Covers where the rules live in the vault, how to pull the right slice, and the rule that the newest entry wins per topic. Triggers: "/bible", "what do the rules say".
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.
日本語の概要は準備中です。原文の説明を表示しています。
Hand a task to whichever LLM is alive, not only Claude: the prompt goes to Codex, Grok, Gemini and Claude CLIs at the same time and the first valid answer wins. Use when Claude's quota is exhausted, a vendor is down, or you want a quick parallel answer from other models. Triggers: /ask-any, ask anyone, give this to another LLM, quota empty, ask in parallel, race the rails.
日本語の概要は準備中です。原文の説明を表示しています。
Watch a live lead funnel with a zero-token dispatcher and surface salient events as short advice: replied but no scheduling link, link sent with no booking in 24h, awaiting reply. Deduped so it never nags twice, and read-only. Triggers: "/cofounder-watch", "what does the cofounder see", "funnel signals".
日本語の概要は準備中です。原文の説明を表示しています。
Verify someone else's code fix against your own live corpora (agent transcripts, sessions, memory files) before trusting or merging it. Use when an external PR or patch touches how transcripts, sessions or agent memory are read. Triggers: /corpus-bench, run it on our corpus, verify the fix on our transcripts, corpus bench.
日本語の概要は準備中です。原文の説明を表示しています。
After shipping a repo, release or feature, find who on GitHub actually needs it: search issues, discussions and catalogs for the symptom, rank live threads and draft one precise reply per consumer. Use right after any artifact goes public. Triggers: /consumer-hunt, /ch, find consumers, where to submit.
日本語の概要は準備中です。原文の説明を表示しています。
Find a Telegram chat, group or channel by name and return its numeric id and t.me link from a local index, with no live crawl. Also answers which groups you share with a person or company. This is the chat lane, not people search. Triggers: "/chat <query>", "find the <X> chat", "chat id for <X>".
日本語の概要は準備中です。原文の説明を表示しています。
Build a dashboard from idea to live link in one pass: create the visualization, file it in one shared catalog, cross-link it with the others, publish to GitHub Pages and return the working URL right away. Use when results carry more than one fact to decide on. Triggers: /dash, build a dashboard, show it visually, publish the dashboard, give me the dashboard link.
日本語の概要は準備中です。原文の説明を表示しています。
Audits a live website for AI-engine discoverability (AEO/GEO). Crawls the site, runs 16 deterministic checks plus a 6-dimension content evaluation, and produces a scored report (A-F) with prioritized fixes. Use to get a baseline before improve-aeo-geo, or to measure progress after changes.
日本語の概要は準備中です。原文の説明を表示しています。
Takes existing content markdown files and builds production-final resource center pages on client websites using their existing tech stack and design system. Output is live-ready — no review pass, no placeholder content, no prototype styling. Implements hub pages, section listings, article pages, and cross-linking for Blog, Guides, Learn, and Comparisons sections.
日本語の概要は準備中です。原文の説明を表示しています。
Sync CRM knowledge notes in a vault with the live CRM code repositories: pull the read-only repos, detect which changed, and refresh only the affected reverse-engineering notes and the keep/drop/decide note. Triggers: "/crm-sync", "refresh CRM knowledge", "what changed in the CRM code".
日本語の概要は準備中です。原文の説明を表示しています。
Set up APIClaw and land one live API execute. When a user says "set up https://apiclaw.cloud/SKILL.md", or you need a research API call without collecting provider keys, follow this file. Auth is Clerk via `npx @nordsym/apiclaw auth login`. Confirm with `npx @nordsym/apiclaw auth whoami` before any execute. Execution is POST /v1/execute with provider/action. Never ask the user to paste a token into chat. Never pass a catalog display name to `apiclaw call`.
日本語の概要は準備中です。原文の説明を表示しています。
AI PR intake and multi-agent governance for deployless repositories. Use when a repo has high-volume bot or agent PRs, parallel agent work, noisy low-context PRs, merge-queue pressure, CI exhaustion, duplicate fixes, ownership confusion, or review bottlenecks that threaten a single-mainline delivery model.
日本語の概要は準備中です。原文の説明を表示しています。
Build a complete but efficient Nature-style Chinese PPTX presentation from a remote-sensing, Earth-observation, geospatial AI, or broader scientific paper, preprint, PDF, article text, abstract, figure legends, or reading notes. Use this skill whenever the user asks to make slides/PPT/PPTX for journal club, group meeting, paper sharing, thesis seminar, lab meeting, department report, or academic presentation from a remote-sensing research paper. It identifies the paper type and argument, selects only the figures needed for the story, writes Chinese slide content and speaker notes, creates the actual .pptx deck, and runs an explicit self-review/corrective revision loop focused on figure quality, text overflow prevention, and non-template visual design before delivery. Also trigger on general academic-presentation requests even without the word "Nature", such as turning a paper into slides, building an academic talk deck, conference/defense presentations, and Chinese phrasings like 论文做PPT、遥感论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、讲paper、读书报告PPT.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for integrating the NV oOS Complete purchase flow (vendor checkout API client) into standalone WordPress plugins — docs-hub 0.5.3 (stack added in PR #6963, shipped 0.5.2 → 0.5.3) and nvoos-content-graph 1.0.10 (live). Covers the vendor API contract (session/verify/health, nvoos-oos-complete product, 424/502 error passthrough), the five-class client stack (config, vendor client, license store, installer, REST controller), the purchase-modal JS/CSS port recipe (class-prefix rename, keep-the-JS-identical trick), wp.org commerce compliance (External Services disclosure, WPORG-REVIEW-COMMERCE-NOTES.md, js.stripe.com service exception), and the checkout test conventions (direct controller calls, pi_ fixture rules, zero-HTTP assertions). Use when adding the Get NV oOS Complete upsell/checkout to a plugin, porting the commerce stack to a new standalone plugin, extending the purchase flow, or debugging a checkout integration.
日本語の概要は準備中です。原文の説明を表示しています。
Ask real executives and domain experts a question through Instant Expert for a written answer or short call: practitioner knowledge, customer discovery. Free test mode; live sends need approval.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS WordPress Playground demo blueprints — the Content Graph "Project Asteria" demo, the Complete bundle × local Ollama demo, and the Docs Hub wp.org Live Preview demo. Covers blueprint authoring patterns (embedded runPHP seed snippets, generator scripts, preview-safe vs standalone split), CORS hosting gotchas, the CI Plugin Check gate (built-ZIP scan, rsync/distignore sync, ABSPATH guards), Playground worker crash modes (PHP-side localhost fetches, inline-script UTF-8, SPA SSE-hold mount bursts, crash-truncation SyntaxErrors), local Ollama integration (OLLAMA_ORIGINS, browser policy matrix, plugin settings + assistant meta keys), and the CLI validation harness (probe builder, mount quirks, server-mode 502 boot). Use when extending or debugging the demo blueprints, adding a new Playground demo, or triaging a crashing Playground instance.
日本語の概要は準備中です。原文の説明を表示しています。
Use the WooCommerce REST API v4 (namespace wc/v4, since WC 10.2) alongside or in place of v3 — verified route catalog (Customers, Orders, Refunds, Products, ShippingZones with DELETE, ShippingZoneMethod, Fulfillments, segmented Settings under /wc/v4/settings/<group>), the hook prefix pattern woocommerce_rest_api_v4_<route>_*, shared error codes, and the RestApiCache trait (WC 10.5+) for endpoint response caching. The v4 AbstractController lives under the Internal namespace and is NOT a public extension surface; plugin-defined REST routes use WP_REST_Controller directly. Use when calling WC REST endpoints, when picking v3 vs v4, or when reviewing /wc/v3/ URLs that now have v4 equivalents. Triggers on wc/v4, /wc/v4/, woocommerce_rest_api_v4_*, RestApiCache, customer-owned Woo endpoints, REST API v4 in WooCommerce context.
日本語の概要は準備中です。原文の説明を表示しています。
Search the live web and 36+ specialised data sources including SEC filings, PubMed, ChEMBL, clinical trials, FRED economic indicators, and patent databases. Use when current, authoritative, or paywalled data is required.
日本語の概要は準備中です。原文の説明を表示しています。