[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KNPKVGANP87FFP1FCR28X":3,"skill-same:01M75KNPKVGANP87FFP1FCR28X":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75KNPKVGANP87FFP1FCR28X","wp-plugin-development",null,"Use when developing WordPress plugins: architecture and hooks, activation\u002Fdeactivation\u002Funinstall, admin UI and Settings API, data storage, cron\u002Ftasks, security (nonces\u002Fcapabilities\u002Fsanitization\u002Fescaping), and release packaging.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: wp-plugin-development\ndescription: \"Use when developing WordPress plugins: architecture and hooks, activation\u002Fdeactivation\u002Funinstall, admin UI and Settings API, data storage, cron\u002Ftasks, security (nonces\u002Fcapabilities\u002Fsanitization\u002Fescaping), and release packaging.\"\ncompatibility: \"Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.\"\n---\n\n# WP Plugin Development\n\n## When to use\n\nUse this skill for plugin work such as:\n\n- creating or refactoring plugin structure (bootstrap, includes, namespaces\u002Fclasses)\n- adding hooks\u002Factions\u002Ffilters\n- activation\u002Fdeactivation\u002Funinstall behavior and migrations\n- adding settings pages \u002F options \u002F admin UI (Settings API)\n- security fixes (nonces, capabilities, sanitization\u002Fescaping, SQL safety)\n- packaging a release (build artifacts, readme, assets)\n\n## Inputs required\n\n- Repo root + target plugin(s) (path to plugin main file if known).\n- Where this plugin runs: single site vs multisite; WP.com conventions if applicable.\n- Target WordPress + PHP versions (affects available APIs and placeholder support in `$wpdb->prepare()`).\n\n## Procedure\n\n### 0) Triage and locate plugin entrypoints\n\n1. Run triage:\n   - `node skills\u002Fwp-project-triage\u002Fscripts\u002Fdetect_wp_project.mjs`\n2. Detect plugin headers (deterministic scan):\n   - `node skills\u002Fwp-plugin-development\u002Fscripts\u002Fdetect_plugins.mjs`\n\nIf this is a full site repo, pick the specific plugin under `wp-content\u002Fplugins\u002F` or `mu-plugins\u002F` before changing code.\n\n### 1) Follow a predictable architecture\n\nGuidelines:\n\n- Keep a single bootstrap (main plugin file with header).\n- Avoid heavy side effects at file load time; load on hooks.\n- Prefer a dedicated loader\u002Fclass to register hooks.\n- Keep admin-only code behind `is_admin()` (or admin hooks) to reduce frontend overhead.\n\nSee:\n- `references\u002Fstructure.md`\n\n### 2) Hooks and lifecycle (activation\u002Fdeactivation\u002Funinstall)\n\nActivation hooks are fragile; follow guardrails:\n\n- register activation\u002Fdeactivation hooks at top-level, not inside other hooks\n- flush rewrite rules only when needed and only after registering CPTs\u002Frules\n- uninstall should be explicit and safe (`uninstall.php` or `register_uninstall_hook`)\n\nSee:\n- `references\u002Flifecycle.md`\n\n### 3) Settings and admin UI (Settings API)\n\nPrefer Settings API for options:\n\n- `register_setting()`, `add_settings_section()`, `add_settings_field()`\n- sanitize via `sanitize_callback`\n\nSee:\n- `references\u002Fsettings-api.md`\n\n### 4) Security baseline (always)\n\nBefore shipping:\n\n- Validate\u002Fsanitize input early; escape output late.\n- Use nonces to prevent CSRF *and* capability checks for authorization.\n- Avoid directly trusting `$_POST` \u002F `$_GET`; use `wp_unslash()` and specific keys.\n- Use `$wpdb->prepare()` for SQL; avoid building SQL with string concatenation.\n\nSee:\n- `references\u002Fsecurity.md`\n\n### 5) Data storage, cron, migrations (if needed)\n\n- Prefer options for small config; custom tables only if necessary.\n- For cron tasks, ensure idempotency and provide manual run paths (WP-CLI or admin).\n- For schema changes, write upgrade routines and store schema version.\n\nSee:\n- `references\u002Fdata-and-cron.md`\n\n## Verification\n\n- Plugin activates with no fatals\u002Fnotices.\n- Settings save and read correctly (capability + nonce enforced).\n- Uninstall removes intended data (and nothing else).\n- Run repo lint\u002Ftests (PHPUnit\u002FPHPCS if present) and any JS build steps if the plugin ships assets.\n\n## Failure modes \u002F debugging\n\n- Activation hook not firing:\n  - hook registered incorrectly (not in main file scope), wrong main file path, or plugin is network-activated\n- Settings not saving:\n  - settings not registered, wrong option group, missing capability, nonce failure\n- Security regressions:\n  - nonce present but missing capability checks; or sanitized input not escaped on output\n\nSee:\n- `references\u002Fdebugging.md`\n\n## Escalation\n\nFor canonical detail, consult the Plugin Handbook and security guidelines before inventing patterns.\n","# WP Plugin Development\n\n## When to use\n\nUse this skill for plugin work such as:\n\n- creating or refactoring plugin structure (bootstrap, includes, namespaces\u002Fclasses)\n- adding hooks\u002Factions\u002Ffilters\n- activation\u002Fdeactivation\u002Funinstall behavior and migrations\n- adding settings pages \u002F options \u002F admin UI (Settings API)\n- security fixes (nonces, capabilities, sanitization\u002Fescaping, SQL safety)\n- packaging a release (build artifacts, readme, assets)\n\n## Inputs required\n\n- Repo root + target plugin(s) (path to plugin main file if known).\n- Where this plugin runs: single site vs multisite; WP.com conventions if applicable.\n- Target WordPress + PHP versions (affects available APIs and placeholder support in `$wpdb->prepare()`).\n\n## Procedure\n\n### 0) Triage and locate plugin entrypoints\n\n1. Run triage:\n   - `node skills\u002Fwp-project-triage\u002Fscripts\u002Fdetect_wp_project.mjs`\n2. Detect plugin headers (deterministic scan):\n   - `node skills\u002Fwp-plugin-development\u002Fscripts\u002Fdetect_plugins.mjs`\n\nIf this is a full site repo, pick the specific plugin under `wp-content\u002Fplugins\u002F` or `mu-plugins\u002F` before changing code.\n\n### 1) Follow a predictable architecture\n\nGuidelines:\n\n- Keep a single bootstrap (main plugin file with header).\n- Avoid heavy side effects at file load time; load on hooks.\n- Prefer a dedicated loader\u002Fclass to register hooks.\n- Keep admin-only code behind `is_admin()` (or admin hooks) to reduce frontend overhead.\n\nSee:\n- `references\u002Fstructure.md`\n\n### 2) Hooks and lifecycle (activation\u002Fdeactivation\u002Funinstall)\n\nActivation hooks are fragile; follow guardrails:\n\n- register activation\u002Fdeactivation hooks at top-level, not inside other hooks\n- flush rewrite rules only when needed and only after registering CPTs\u002Frules\n- uninstall should be explicit and safe (`uninstall.php` or `register_uninstall_hook`)\n\nSee:\n- `references\u002Flifecycle.md`\n\n### 3) Settings and admin UI (Settings API)\n\nPrefer Settings API for options:\n\n- `register_setting()`, `add_settings_section()`, `add_settings_field()`\n- sanitize via `sanitize_callback`\n\nSee:\n- `references\u002Fsettings-api.md`\n\n### 4) Security baseline (always)\n\nBefore shipping:\n\n- Validate\u002Fsanitize input early; escape output late.\n- Use nonces to prevent CSRF *and* capability checks for authorization.\n- Avoid directly trusting `$_POST` \u002F `$_GET`; use `wp_unslash()` and specific keys.\n- Use `$wpdb->prepare()` for SQL; avoid building SQL with string concatenation.\n\nSee:\n- `references\u002Fsecurity.md`\n\n### 5) Data storage, cron, migrations (if needed)\n\n- Prefer options for small config; custom tables only if necessary.\n- For cron tasks, ensure idempotency and provide manual run paths (WP-CLI or admin).\n- For schema changes, write upgrade routines and store schema version.\n\nSee:\n- `references\u002Fdata-and-cron.md`\n\n## Verification\n\n- Plugin activates with no fatals\u002Fnotices.\n- Settings save and read correctly (capability + nonce enforced).\n- Uninstall removes intended data (and nothing else).\n- Run repo lint\u002Ftests (PHPUnit\u002FPHPCS if present) and any JS build steps if the plugin ships assets.\n\n## Failure modes \u002F debugging\n\n- Activation hook not firing:\n  - hook registered incorrectly (not in main file scope), wrong main file path, or plugin is network-activated\n- Settings not saving:\n  - settings not registered, wrong option group, missing capability, nonce failure\n- Security regressions:\n  - nonce present but missing capability checks; or sanitized input not escaped on output\n\nSee:\n- `references\u002Fdebugging.md`\n\n## Escalation\n\nFor canonical detail, consult the Plugin Handbook and security guidelines before inventing patterns.\n",{"name":5,"description":7,"compatibility":23},"Targets WordPress 6.9+ (PHP 7.2.24+). Filesystem-based agent with bash + node. Some workflows require WP-CLI.","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fwp-plugin-development",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill wp-plugin-development",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill wp-plugin-development",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill wp-plugin-development","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002FSKILL.md",true,[47,53,57,61,65,69,73],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fdata-and-cron.md","REFERENCE","参考文档",678,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Fdata-and-cron.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fdebugging.md",559,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Fdebugging.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Flifecycle.md",854,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Flifecycle.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fsecurity.md",787,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Fsecurity.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fsettings-api.md",703,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Fsettings-api.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fstructure.md",401,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Freferences\u002Fstructure.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fdetect_plugins.mjs","SCRIPT","脚本",2842,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fwp-plugin-development\u002Fscripts\u002Fdetect_plugins.mjs",[80,87,94,103,110,117],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":98,"licenseFileUrl":99,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]