7,365 件 ・ 関連度順
概要と使いどころ
- Establish who registered and who operates a domain using WHOIS, RDAP and DNS. Use when running a whois lookup, querying RDAP, digging A, AAAA, MX, NS, TXT, SOA or CAA records, reading SPF includes, DKIM selectors or DMARC rua addresses, finding the registrar, registrant or nameservers, doing reverse DNS, PTR, ASN or netblock lookups, or hunting historical WHOIS and passive DNS
日本語の概要は準備中です。原文の説明を表示しています。
Assemble a full multi-tier content episode from a milestone session's hot context and publish it out of band, ahead of the nightly schedule: teasers go to chats right after one approval, the rest follow by topology. Triggers: "/wow", "this is a milestone", "this session is great, tell everyone".
日本語の概要は準備中です。原文の説明を表示しています。
- End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator
日本語の概要は準備中です。原文の説明を表示しています。
Run an investor-outreach wave end to end: assemble the batch of targets, personalize pitches from real templates, send from the designated account, and log every touch in the CRM. Walks the exact checklist with rate limits and dedup against everyone already contacted. Triggers: "/notpeople-wave", "next outreach batch".
日本語の概要は準備中です。原文の説明を表示しています。
Answer 'what happened on that day' instantly from a daily ledger that night robots assemble from free traces (git commits, session logs, vault writes, bus messages), with zero LLM tokens spent on retrieval. Use when asked what was done yesterday, on a given date or during a week. Triggers: /ledger, what did we do yesterday, what happened on <date>, show the day, daily summary.
日本語の概要は準備中です。原文の説明を表示しています。
- Use people-search aggregators and primary public records to find addresses, phone numbers, relatives, age and background on a person, and to audit and remove your own exposure. Use when running a people search or reverse address lookup, tracing a debtor or missing person, building a subject's address history, or removing yourself from broker sites
日本語の概要は準備中です。原文の説明を表示しています。
- Trace cryptocurrency addresses and transactions on public blockchains using block explorers including Etherscan, Blockchair, mempool.space and Blockscout. Use when following a Bitcoin or Ethereum wallet, investigating where a ransom or scam payment went, or checking an address against sanctions listings
日本語の概要は準備中です。原文の説明を表示しています。
Search inside past agent sessions and continue the one that matters with a single command. Uses a separate episodic session index, so raw chat noise never pollutes the curated RAG. Triggers: "/chat-search", "which chat discussed X", "did we already research X", "search old chats".
日本語の概要は準備中です。原文の説明を表示しています。
Read-only measurement of an agent's autonomy debt from its approvals log: how many times it asked the human for permission in a window, how many asks expired unanswered, and which classes they fall into (machine noise, login or 2FA, physical UAC, money). Use to find asks the agent should have decided itself and to cut needless interruptions. Triggers: /ask-debt, autonomy debt, how often do I ask, expired asks.
日本語の概要は準備中です。原文の説明を表示しています。
Plan browser, app, screenshot, or UI checks before visual claims. Use when a task includes app shots, visual QA, generated assets, or runtime UI proof.
日本語の概要は準備中です。原文の説明を表示しています。
Use for dedicated mobile, tablet, ultrawide, touch, or breakpoint design passes where content priority, layout, navigation, imagery, interaction, and motion must be recomposed rather than simply resized.
日本語の概要は準備中です。原文の説明を表示しています。
Use when converting a design direction into maintainable production frontend code, selecting architecture within the existing stack, implementing semantics, assets, loading behavior, CSS/layout, components, and progressive enhancement.
日本語の概要は準備中です。原文の説明を表示しています。
当用户在纠结"该不该投KOL""预算该花在渠道还是内容上""是不是找到关键人物就能引爆传播"时调用此 skill。核心信号：用户在讨论KOL投放策略、影响者营销预算分配、是否需要找"对的人"来传播。不适用于：渠道运营的纯执行决策（如选哪个KOL）、B2B大客户销售（关系驱动而非传播驱动）、品牌代言人长期签约（品牌形象考量而非传播考量）。关键触发：涉及"KOL值不值得投""预算花在渠道还是内容""引爆传播靠什么"的讨论。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the NV oOS Dictation desktop companion app (Tauri v2 + Rust, examples/nvoos-dictate) — build/run on Windows/MSVC, the local-first engine track (parakeet/whisper/moonshine/silero-vad, all API-verified against pinned crate versions), the embedded remote-STT fallback against the Embedded addon's transcribe route, model registry + verification harnesses, the plugins.updater boot-crash config rule, and the full test/clippy gate matrix. Use when building, extending, or debugging the dictation app, adding an engine or model, touching the cleanup pipeline golden tests, or continuing the P2/P4/P5/distribution follow-up work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building custom agent backends, implementing the AG-UI protocol, debugging streaming issues, or understanding how agents communicate with frontends. Covers event types, SSE transport, AbstractAgent/HttpAgent patterns, state synchronization, tool calls, and human-in-the-loop flows.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for the three recurring NV oOS maintenance tracks: (1) Docs & Release Catch-Up — plan-first per-version docs, changelog, and version-bump passes; (2) Model Catalog & Config Updates — the monthly model-config refresh across the catalog and its derived files; (3) PR Deferred-Item Sweep — review merged/closed PRs for deferred work and file GitHub issues for what is still incomplete. Use when asked to 'catch up docs', 'update the model configs', or 'review the week's PRs for deferred work'.
日本語の概要は準備中です。原文の説明を表示しています。
Adds a per-form settings panel to the JetFormBuilder Gutenberg form editor sidebar — registers REST-exposed post meta on the form CPT, enqueues a block-editor JS bundle, and registers a panel via the JFB-specific 'jet.fb.register.plugins' filter using @wordpress/components (TextControl, SelectControl, ToggleControl) and JFB's useMetaState hook for two-way binding to post meta. Use when a companion plugin needs settings that vary per form (e.g. upload folder, file size limit, integration target) instead of (or in addition to) site-wide defaults from the global Settings page. Triggers on mentions of "JFB form sidebar", "JFB form settings panel", "form-level settings", "useMetaState", "jet.fb.register.plugins", "jet-form-builder/editor-assets/before", or scaffolding a JFB companion plugin that needs per-form config.
日本語の概要は準備中です。原文の説明を表示しています。
Operational guide for WordPress.org submission readiness of NV oOS standalone plugins (nvoos-docs-hub live at 0.5.3; nvoos-content-graph live at 1.0.10 in the re-submission loop; nvoos-design-system next in the pipeline — issue #6811). Covers the 18 wp.org guidelines, the Plugin Check (PCP) gate in CI and Docker, PCP finding triage, the reviewer-reply loop (findings taxonomy from the real 0.4.3 review, related-issue sweep checklist, reply-email template), packaging exclusion tri-sync, readme.txt standards, .wordpress-org listing assets, and the NV oOS Complete checkout-flow disclosure discipline (docs-hub 0.5.3, content-graph). Use when preparing a wp.org submission, responding to a reviewer email, fixing the plugin-check CI job, triaging PCP findings, or capturing listing screenshots.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Per-toolkit hardening audit loop for NV oOS Pro tools. Systematically scans each addons/pro/includes/tools/<toolkit> (and its plugins/nvoos-content-graph-pro mirror) for the four recurring production failure classes — unguarded shell calls that fatal on exec-disabled hosts, calls to nonexistent client methods, string-assuming parsing of provider responses that may be arrays, and provider enum/service mismatches — then fixes, tests (Docker PHPUnit), and validates (phpcs both standards) before moving to the next toolkit. Use when asked to audit a toolkit, review the X tools for similar issues, do the same for the other toolkits, or continue the toolkit audit loop. The first case study (document-generation) found 3 fatal bugs + 1 broken regex.
日本語の概要は準備中です。原文の説明を表示しています。
Design and review native presenter classes in WordPress plugins without requiring better-data - converting DTOs or domain objects into REST arrays, admin table rows, JS config payloads, email variables, and public view models with allowlisted fields, context methods, redaction by default, locale/date/number formatting, no DTO mutation, and correct WordPress escaping boundaries. Use when adding FooPresenter, response mappers, admin-row arrays, wp_send_json payloads, rest_ensure_response data, wp_add_inline_script config, or when code returns raw DTOs, WP_Post, WC_Order, get_object_vars, json_encode, or unescaped HTML from controllers.
日本語の概要は準備中です。原文の説明を表示しています。
Design and review native DTOs in WordPress plugins without requiring better-data - immutable data carriers, explicit from_array hydration, strict coercion instead of unchecked casts, WP_Error validation failures, sensitive-field discipline, nested DTO arrays, and clear separation from repositories, WP models, presenters, REST controllers, and HTML views. Use when a plugin introduces FooDto, request DTOs, settings DTOs, value objects, admin-row data shapes, REST response source objects, or when reviewing code that passes raw arrays, stdClass, WP_Post, WC_Order, $_POST, post meta, or option arrays through multiple layers. Mentions better-data only as an optional higher-level library; this skill is for native implementations.
日本語の概要は準備中です。原文の説明を表示しています。
Define product photography standards for e-commerce — shot types, composition, lighting, consistency rules, AI-assisted generation, and platform-specific variants. Covers the full product imagery pipeline from concept to published asset. Use when you need to plan product photoshoots, create photography briefs, set image standards for an e-commerce catalog, generate AI product lifestyle shots, or ensure visual consistency across hundreds of products.
日本語の概要は準備中です。原文の説明を表示しています。