查找技能

Autonomous driver loop for ExploitHunter vulnerability-research campaigns. Runs breadth-first waves of research lanes on rented hosts with no per-request human approval, steers lanes via the shared Investigation Graph (demoting dead ends, respawning on high-signal priorities), saturates host capacity, and enforces wave/budget/safety discipline. Use when driving a multi-target bug-hunting campaign, launching parallel research lanes, or resuming a campaign from a state snapshot.

中文简介正在准备中。当前显示原文说明。

Use when exposing a WordPress site to AI agents via MCP, or when WordPress MCP setup fails.

中文简介正在准备中。当前显示原文说明。

Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.

中文简介正在准备中。当前显示原文说明。

Give a project a GitHub-releases updater. Use when a release ships unoffered, or a hand-copied updater moves to vendor/.

中文简介正在准备中。当前显示原文说明。

Write a document an agent consumes — a skill, an AGENTS.md, a README, a docblock, or any file reached by a pointer.

中文简介正在准备中。当前显示原文说明。

Remove AI tells from English prose — a README, a comment, a user-facing string, a review. French is `humaniseur-fr`.

中文简介正在准备中。当前显示原文说明。

Translate between French and US English — i18n strings, a French reply to the owner, an existing translation.

中文简介正在准备中。当前显示原文说明。

Remove AI tells from French prose without lowering its register — a reply, a `.po` target, a French post.

中文简介正在准备中。当前显示原文说明。

Write anything a person reads — a README, a changelog, a commit message, a docblock. Carries the WordPress Style Guide.

中文简介正在准备中。当前显示原文说明。

Write a test that can fail. Use when adding a test, creating a suite, raising coverage, or claiming behavior is covered.

中文简介正在准备中。当前显示原文说明。

Standard Operating Procedures for backend development, bug fixing, DevOps, infrastructure deployment, and security hardening.

中文简介正在准备中。当前显示原文说明。

Integration review of stable code: a review note and a fix list, no implementation. Use before shipping.

中文简介正在准备中。当前显示原文说明。

Hostile, WordPress-specialized QA audit: severity-ranked findings, never a fix. Use for an adversarial audit.

中文简介正在准备中。当前显示原文说明。

Cut a release: version bump, readme.txt, changelog, build, Plugin Check, zip. The owner must authorize the bump.

中文简介正在准备中。当前显示原文说明。

Audits a website codebase and makes code changes so AI engines (ChatGPT, Claude, Perplexity, Google AI Overviews) can better discover, parse, quote, and cite the site. Covers structured data, content structure, technical signals, and freshness.

中文简介正在准备中。当前显示原文说明。

Analyze GTmetrix (and PageSpeed) reports for WordPress sites and produce a prioritized optimization plan, a custom WPCode-ready PHP optimization snippet, and a self-contained HTML summary report. Covers PDF report extraction with pypdf, live-page cross-referencing, WordPress-specific fix mapping (Elementor, WooCommerce, Breeze, reCAPTCHA, Google-tag duplication, WebP conversion), and staging-test discipline. Use when asked to review GTmetrix reports, optimize page speed or Core Web Vitals, create a custom performance optimization snippet, or produce an optimization report for a WordPress site.

中文简介正在准备中。当前显示原文说明。

Operational guide for the NV oOS Model Foundry (Proposal 067) — the cluster fine-tuning flywheel. Phase 1 shipped: the Corpus Foundry (Pro addon, addons/pro/includes/model-foundry/) — consent-gated, deduplicated, PII-scrubbed corpus exporters (trajectory_v1, preference_v1, docs_v1) with deterministic holdout splits and R12 provenance manifests. Covers the governance contract, row schemas, output layout, filter seams, the registration pattern for foundry tool slices, how to add a new exporter, and the test/validation gates. Use when extending the Corpus Foundry, debugging corpus exports, wiring a new data source, or continuing Phases 2–6 (train-worker, registry/serving, eval gate, fleet sharing).

中文简介正在准备中。当前显示原文说明。

End-to-end playbook for creating a new NV oOS Pro toolkit under addons/pro/includes/tools/<toolkit> — folder layout, service layer, tool class conventions (canonical envelope, two-gate sanitisation, capability flags), ALL eleven registration surfaces (Pro module registry loader, central registry, admin Tools section + Features subtab, admin settings page/side menu, settings status map, both WP-CLI commands, schedule presets, workflow presets, SA Toolkit Manager, coverage manifests), fixture/oracle testing with a standalone smoke harness, and the phpcs gotcha checklist. Use when asked to build a new Pro toolkit, add a toolkit to the plugin, scaffold toolkit tools, register toolkit presets/toggles, or debug why a new toolkit's tools, toggle, or admin menu don't appear. First case study: food-beverage (F&B Management, 21 tools, 2026-10-08, 20/20 Check-totals oracle verified). Complements mcp-ai-wpoos-toolkit-audit (hardening existing toolkits) and mcp-ai-wpoos-test-suite (repair).

中文简介正在准备中。当前显示原文说明。

Manage AI assistant configurations and peer-to-peer mesh network connections in the NV oOS Pro Toolkit. Covers assistant creation, model configuration, provider setup, peer discovery, mesh networking, and cross-assistant communication. Use when creating or editing AI assistants, configuring model providers, setting up peer connections, managing mesh network topology, or debugging assistant behavior.

中文简介正在准备中。当前显示原文说明。

UI stack, build, and test conventions for NV oOS React SPA addons (toolkit-shell, chat-spa, schedule-anything-spa, saas-controller) — three sanctioned build patterns plus the standalone Pro SPA Vite app (examples/nvoos-pro-spa-vite), dual-React guard, headless component rules, NDS tokens, Tailwind v4, @xyflow/react v12, vitest/jsdom gotchas, the full-JS-rebuild map, and the TS-shadows-JS webpack gotcha. Use when building or modifying SPA addon UI, writing SPA JS tests, upgrading SPA deps, or rebuilding JS for packaging.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。

Operate NV oOS WordPress sites through the NV oOS MCP Gateway — namespaced tools, key scoping, background research, and health checks. Use when working with tools prefixed <site-slug>.<tool> or when asked about the gateway.

中文简介正在准备中。当前显示原文说明。

Agentic design-to-build pipeline that turns a Figma design into a built WordPress site using the Figma MCP server (read side) and the Elementor MCP server (write side) attached as MCP Apps on an NV oOS assistant. Covers the 7-stage pipeline (Scope → Read → Plan → Tokenize → Build → Verify → Handoff), the normative stage rules (get_design_context first, tokenize before build, drafts only, never publish, Figma read-only), the build-manifest contract (schema + example in reference/build-manifest.md), the design-file contract (frame/section/variable naming in reference/design-file-contract.md), assistant wiring (figma + elementor MCP Apps, OAuth + application passwords, host allowlist), safety rules, and troubleshooting. Use when asked to build or create a site, page, or landing page from a Figma design, to wire Figma MCP or Elementor MCP for design-to-build work, to approve or produce a build manifest, or to debug a failed design-to-build run.

中文简介正在准备中。当前显示原文说明。

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.

中文简介正在准备中。当前显示原文说明。