[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72WM48CZ1W9EPKM7X4D3GE1":3,"skill-same:01M72WM48CZ1W9EPKM7X4D3GE1":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M72WM48CZ1W9EPKM7X4D3GE1","wp-plugin-directory-guidelines",null,"Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell\u002Ffreemium\u002Ftrialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.","procyon-creative\u002Fwp-dario-provider","procyon-creative","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108539561?v=4","01M72WGVJQCTY3JENE9DDREJ61","Procyon Creative","01M72WGVKC11SWCNQBV05FHJ6D",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-plugin-directory-guidelines\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: wp-plugin-directory-guidelines\ndescription: \"Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell\u002Ffreemium\u002Ftrialware patterns, validating plugin naming or trademark rules, checking plugin slugs, understanding why a plugin was rejected from WordPress.org, or answering any question about the 18 WordPress.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.\"\ncompatibility: \"Targets WordPress 7.0+ (PHP 7.4.0+).\"\n---\n\n## Overview\n\nAuthoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming\u002Ftrademark rules, trialware restrictions, and all other submission requirements.\n\n## When to use\n\nUse this skill when you need to:\n- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines\n- Check GPL license compatibility for a plugin or its bundled libraries\n- Verify license headers in plugin files\n- Identify common guideline violations before submission\n- Answer questions about what is or is not allowed on WordPress.org\n- Evaluate premium\u002Fupsell flows, license checks, or freemium positioning\n- Review \"teaser\" or \"preview\" UI for trialware violations\n\n## Inputs required\n\n- Plugin source code (or specific files to review)\n- Optional: plugin readme and plugin header metadata for naming and license checks\n\n## Procedure\n\n1. Check the plugin's license header against the **Valid License Headers** section below.\n2. Walk through the **18 Guidelines** checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.\n3. Confirm trialware\u002Ffreemium compliance using the checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md) (Guideline 5 section).\n4. For bundled third-party code, verify license compatibility against **GPL-Compatible Licenses (Quick)** below.\n5. Flag matches from **Common GPL Violations (Quick)** below.\n6. For edge cases, consult the detailed references and the [GNU GPL FAQ](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-faq.html).\n\n## 18-Guideline Review Checklist\n\nUse the detailed, per-guideline checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md). Load this reference file only when a full guideline audit is requested.\n\n## GPL Compliance (Guideline 1 in Detail)\n\nUse [gpl-compliance.md](references\u002Fgpl-compliance.md) for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.\n\n### Verification (Licensing)\n\n- Every licensing-related issue must cite **Guideline 1** and include the file path and exact license string.\n- Confirm compatibility claims against **GPL-Compatible Licenses (Quick)** and escalate ambiguous licenses.\n\n### Failure modes (Licensing)\n\n- If a license is not clearly GPL-compatible, do not guess. Check the [GNU license list](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Flicense-list.html).\n- For dual-license packages, verify both licenses and redistribution terms.\n\n### Quick Reference: WordPress GPL Requirements\n\n- WordPress is **GPLv2 or later**.\n- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).\n- Include a valid `License:` header and `License URI:` in the main plugin file.\n- Do not add restrictions that conflict with GPL freedoms.\n\n### Valid License Headers\n\n## GPL Versions Summary\n\n| Version | Year | Key Addition |\n|---------|------|--------------|\n| GPLv1 | 1989 | Base copyleft: share-alike for modifications |\n| GPLv2 | 1991 | \"Liberty or death\" clause (Section 7), clearer distribution terms |\n| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |\n\nWordPress uses **GPLv2 or later**, meaning plugins can use GPLv2, GPLv3, or \"GPLv2 or later\".\n\nFor full license texts, see:\n- [GNU General Public License v1](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-1.0.html)\n- [GNU General Public License v2](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html)\n- [GNU General Public License v3](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html)\n\n## License Compliance Checklist\n\nWhen reviewing a plugin, verify:\n\n- [ ] Main plugin file has a valid `License:` header (e.g., `GPL-2.0-or-later`, `GPL-2.0+`, `GPLv2 or later`)\n- [ ] Main plugin file has a `License URI:` header pointing to the GPL text\n- [ ] If bundled libraries exist, each has a GPL-compatible license\n- [ ] No \"split licensing\" (e.g., code GPL but premium features proprietary)\n- [ ] No additional restrictions beyond what GPL allows\n- [ ] No clauses restricting commercial use, modification, or redistribution\n- [ ] No obfuscated code (violates the spirit of source code availability)\n\n## Valid License Headers for WordPress Plugins\n\n```\nLicense: GPL-2.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n```text\nLicense: GPL-3.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html\n```\n\n```text\nLicense: GPLv2 or later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n### GPL-Compatible Licenses (Quick)\n\n- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.\n- Commonly accepted permissive families: MIT\u002FExpat, BSD, ISC, zlib, Boost.\n- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).\n- For full accepted and rejected identifiers, use [gpl-compliance.md](references\u002Fgpl-compliance.md).\n\n### Common GPL Violations (Quick)\n\n- Split licensing that restricts distributed code.\n- Obfuscated or non-corresponding source distribution.\n- Restrictive clauses (non-commercial, no-resale, forced backlink).\n- Bundling GPL-incompatible libraries or assets.\n\n## Plugin Naming Rules (Guideline 17)\n\nUse [naming-rules.md](references\u002Fnaming-rules.md) for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.\n\n### Naming Checklist (Quick)\n\n- Name is not a placeholder and has at least 5 alphanumeric characters.\n- Header name and readme name match.\n- Name is specific and function-related; avoid keyword stuffing.\n- Trademark\u002Fproject names appear only after connectors like `for`, `with`, `using`, `and`.\n- No banned\u002Fdiscouraged terms or trademark portmanteaus.\n- Slug is lowercase, hyphenated, \u003C= 50 chars, and avoids blocked terms.\n","## Overview\n\nAuthoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming\u002Ftrademark rules, trialware restrictions, and all other submission requirements.\n\n## When to use\n\nUse this skill when you need to:\n- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines\n- Check GPL license compatibility for a plugin or its bundled libraries\n- Verify license headers in plugin files\n- Identify common guideline violations before submission\n- Answer questions about what is or is not allowed on WordPress.org\n- Evaluate premium\u002Fupsell flows, license checks, or freemium positioning\n- Review \"teaser\" or \"preview\" UI for trialware violations\n\n## Inputs required\n\n- Plugin source code (or specific files to review)\n- Optional: plugin readme and plugin header metadata for naming and license checks\n\n## Procedure\n\n1. Check the plugin's license header against the **Valid License Headers** section below.\n2. Walk through the **18 Guidelines** checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.\n3. Confirm trialware\u002Ffreemium compliance using the checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md) (Guideline 5 section).\n4. For bundled third-party code, verify license compatibility against **GPL-Compatible Licenses (Quick)** below.\n5. Flag matches from **Common GPL Violations (Quick)** below.\n6. For edge cases, consult the detailed references and the [GNU GPL FAQ](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-faq.html).\n\n## 18-Guideline Review Checklist\n\nUse the detailed, per-guideline checklist in [guideline-review-checklist.md](references\u002Fguideline-review-checklist.md). Load this reference file only when a full guideline audit is requested.\n\n## GPL Compliance (Guideline 1 in Detail)\n\nUse [gpl-compliance.md](references\u002Fgpl-compliance.md) for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.\n\n### Verification (Licensing)\n\n- Every licensing-related issue must cite **Guideline 1** and include the file path and exact license string.\n- Confirm compatibility claims against **GPL-Compatible Licenses (Quick)** and escalate ambiguous licenses.\n\n### Failure modes (Licensing)\n\n- If a license is not clearly GPL-compatible, do not guess. Check the [GNU license list](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Flicense-list.html).\n- For dual-license packages, verify both licenses and redistribution terms.\n\n### Quick Reference: WordPress GPL Requirements\n\n- WordPress is **GPLv2 or later**.\n- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).\n- Include a valid `License:` header and `License URI:` in the main plugin file.\n- Do not add restrictions that conflict with GPL freedoms.\n\n### Valid License Headers\n\n## GPL Versions Summary\n\n| Version | Year | Key Addition |\n|---------|------|--------------|\n| GPLv1 | 1989 | Base copyleft: share-alike for modifications |\n| GPLv2 | 1991 | \"Liberty or death\" clause (Section 7), clearer distribution terms |\n| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |\n\nWordPress uses **GPLv2 or later**, meaning plugins can use GPLv2, GPLv3, or \"GPLv2 or later\".\n\nFor full license texts, see:\n- [GNU General Public License v1](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-1.0.html)\n- [GNU General Public License v2](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html)\n- [GNU General Public License v3](https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html)\n\n## License Compliance Checklist\n\nWhen reviewing a plugin, verify:\n\n- [ ] Main plugin file has a valid `License:` header (e.g., `GPL-2.0-or-later`, `GPL-2.0+`, `GPLv2 or later`)\n- [ ] Main plugin file has a `License URI:` header pointing to the GPL text\n- [ ] If bundled libraries exist, each has a GPL-compatible license\n- [ ] No \"split licensing\" (e.g., code GPL but premium features proprietary)\n- [ ] No additional restrictions beyond what GPL allows\n- [ ] No clauses restricting commercial use, modification, or redistribution\n- [ ] No obfuscated code (violates the spirit of source code availability)\n\n## Valid License Headers for WordPress Plugins\n\n```\nLicense: GPL-2.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n```text\nLicense: GPL-3.0-or-later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-3.0.html\n```\n\n```text\nLicense: GPLv2 or later\nLicense URI: https:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.html\n```\n\n### GPL-Compatible Licenses (Quick)\n\n- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.\n- Commonly accepted permissive families: MIT\u002FExpat, BSD, ISC, zlib, Boost.\n- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).\n- For full accepted and rejected identifiers, use [gpl-compliance.md](references\u002Fgpl-compliance.md).\n\n### Common GPL Violations (Quick)\n\n- Split licensing that restricts distributed code.\n- Obfuscated or non-corresponding source distribution.\n- Restrictive clauses (non-commercial, no-resale, forced backlink).\n- Bundling GPL-incompatible libraries or assets.\n\n## Plugin Naming Rules (Guideline 17)\n\nUse [naming-rules.md](references\u002Fnaming-rules.md) for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.\n\n### Naming Checklist (Quick)\n\n- Name is not a placeholder and has at least 5 alphanumeric characters.\n- Header name and readme name match.\n- Name is specific and function-related; avoid keyword stuffing.\n- Trademark\u002Fproject names appear only after connectors like `for`, `with`, `using`, `and`.\n- No banned\u002Fdiscouraged terms or trademark portmanteaus.\n- Slug is lowercase, hyphenated, \u003C= 50 chars, and avoids blocked terms.\n",{"name":5,"description":7,"compatibility":24},"Targets WordPress 7.0+ (PHP 7.4.0+).","main","f817b1049ffbf34e5609b8222a18dd91365c08fc",".agents\u002Fskills\u002Fwp-plugin-directory-guidelines","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider","https:\u002F\u002Fgithub.com\u002Fprocyon-creative","procyoncreative.com","2026-10-08 08:08:11",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add procyon-creative\u002Fwp-dario-provider --skill wp-plugin-directory-guidelines",{"tool":38,"command":39},"bunx","bunx skills add procyon-creative\u002Fwp-dario-provider --skill wp-plugin-directory-guidelines",{"tool":41,"command":42},"pnpm","pnpm dlx skills add procyon-creative\u002Fwp-dario-provider --skill wp-plugin-directory-guidelines","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-plugin-directory-guidelines\u002FSKILL.md",true,[46,52,56],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fgpl-compliance.md","REFERENCE","参考文档",10342,"https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fgpl-compliance.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fguideline-review-checklist.md",25561,"https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fguideline-review-checklist.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fnaming-rules.md",7003,"https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-plugin-directory-guidelines\u002Freferences\u002Fnaming-rules.md",[61,68,75,82,89,96],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M72WMR8AJ6E3XP3BPW1RVZ6Y","writing-shape","Writing, exploit: shape raw material into an article, paragraph by paragraph.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-shape\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M72WMQ162SMJ423XYP93VK0G","writing-fragments","Writing, explore: mine raw fragments, no structure yet.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-fragments\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M72WMN27YT9F31ZTTRZ898NN","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M72WMKJEJQXHR67PW7KEE5YB","writing-beats","Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwriting-beats\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M72WMHMM3GQD4P2TJ3EQQCC5","wpds","Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwpds\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M72WMECG0CCPPSQ1BTCFWY7E","wp-wpcli-and-ops","Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export\u002Fimport, plugin\u002Ftheme\u002Fuser\u002Fcontent management, cron, cache flushing, multisite, and scripting\u002Fautomation with wp-cli.yml.","https:\u002F\u002Fgithub.com\u002Fprocyon-creative\u002Fwp-dario-provider\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fwp-wpcli-and-ops\u002FSKILL.md",[],[]]