Paper to Chinese Patent Drafter
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…
Install Wp Plugin Directory Guidelines
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelines --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .claude/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .claude/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelinesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .agents/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .agents/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .cursor/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .cursor/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/gambitph/Stackable.git --path .cursor/skills/wp-plugin-directory-guidelines--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .gemini/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .gemini/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelinesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .github/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .github/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install gambitph/Stackable wp-plugin-directory-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/gambitph/Stackable.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/wp-plugin-directory-guidelines .opencode/skills/wp-plugin-directory-guidelines && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wp-plugin-directory-guidelines" agent skill from https://github.com/gambitph/Stackable/tree/develop/.cursor/skills/wp-plugin-directory-guidelines into .opencode/skills/wp-plugin-directory-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wp-plugin-directory-guidelines", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wp-plugin-directory-guidelines- GitHub stars
- 350
- Used in
- 1 other repo
- Token cost
- ~1.6k tokens
- SKILL.md length
- 638 words
- Files
- 4 (incl. references)
- Skills in repo
- 18
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…
- Works in 6 steps: Check the plugin's license header… → Walk through the 18 Guidelines… → Confirm trialware/freemium compliance… → …
- Reviewing WordPress plugins for GPL compliance
- SKILL.md covers Overview, When to use, Inputs required and Procedure, plus 6 more sections
- Reaches gnu.org
What it does
Wp Plugin Directory Guidelines is an agent skill from gambitph/Stackable. Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware 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.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/gpl-compliance.md`, `references/guideline-review-checklist.md` and `references/naming-rules.md`). Compatibility notes: Targets WordPress 7.0+ (PHP 7.4.0+).
It sits in Legal & Compliance, covering Intellectual property. It works with WordPress. The repository describes itself as: Page Builder Blocks for WordPress. An Amazing Block Library for the new WordPress Block Editor (Gutenberg). The licence is GPL-3.0.
When your agent uses it
- Reviewing WordPress plugins for GPL compliance
- Checking license headers
- Evaluating upsell/freemium/trialware patterns
- Validating plugin naming
Example prompts
- “t mention”
- “/wp-plugin-directory-guidelines”
Requirements
- Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+).
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Check the plugin's license header against the Valid License Headers section below.
- Walk through the 18 Guidelines checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
- Confirm trialware/freemium compliance using the checklist in guideline-review-checklist.md (Guideline 5 section).
- For bundled third-party code, verify license compatibility against GPL-Compatible Licenses (Quick) below.
- Flag matches from Common GPL Violations (Quick) below.
- For edge cases, consult the detailed references and the GNU GPL FAQ.
What it can do on your machine
Read from SKILL.md and the folder at commit 5c13d80. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
gnu.org
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Targets WordPress 7.0+ (PHP 7.4.0+).
From compatibility in the SKILL.md frontmatter.
Context cost
Wp Plugin Directory Guidelines loads about 1.6k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 112 tokens; SKILL.md has 638 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from gambitph/Stackable at commit 5c13d80, republished under its GPL-3.0 licence (© gambitph). 638 words, ~1,550 tokens.
Download SKILL.mdSave it as
.claude/skills/wp-plugin-directory-guidelines/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- wp-plugin-directory-guidelines
- description
- Use when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware 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.
- compatibility
- Targets WordPress 7.0+ (PHP 7.4.0+).
Overview
Authoritative reference for the 18 WordPress.org Plugin Directory guidelines. Covers GPL licensing, plugin naming/trademark rules, trialware restrictions, and all other submission requirements.
When to use
Use this skill when you need to:
- Review a WordPress plugin for compliance with the WordPress.org Plugin Directory guidelines
- Check GPL license compatibility for a plugin or its bundled libraries
- Verify license headers in plugin files
- Identify common guideline violations before submission
- Answer questions about what is or is not allowed on WordPress.org
- Evaluate premium/upsell flows, license checks, or freemium positioning
- Review "teaser" or "preview" UI for trialware violations
Inputs required
- Plugin source code (or specific files to review)
- Optional: plugin readme and plugin header metadata for naming and license checks
Procedure
- Check the plugin's license header against the Valid License Headers section below.
- Walk through the 18 Guidelines checklist, paying special attention to Guidelines 1, 4, 5, 7, 8, and 17.
- Confirm trialware/freemium compliance using the checklist in guideline-review-checklist.md (Guideline 5 section).
- For bundled third-party code, verify license compatibility against GPL-Compatible Licenses (Quick) below.
- Flag matches from Common GPL Violations (Quick) below.
- For edge cases, consult the detailed references and the GNU GPL FAQ.
18-Guideline Review Checklist
Use the detailed, per-guideline checklist in guideline-review-checklist.md. Load this reference file only when a full guideline audit is requested.
GPL Compliance (Guideline 1 in Detail)
Use gpl-compliance.md for full license tables, compatibility nuances, and examples. Keep this inline section as a quick decision aid.
Verification (Licensing)
- Every licensing-related issue must cite Guideline 1 and include the file path and exact license string.
- Confirm compatibility claims against GPL-Compatible Licenses (Quick) and escalate ambiguous licenses.
Failure modes (Licensing)
- If a license is not clearly GPL-compatible, do not guess. Check the GNU license list.
- For dual-license packages, verify both licenses and redistribution terms.
Quick Reference: WordPress GPL Requirements
- WordPress is GPLv2 or later.
- Plugins distributed on WordPress.org must be 100% GPL-compatible (code and assets).
- Include a valid
License:header andLicense URI:in the main plugin file. - Do not add restrictions that conflict with GPL freedoms.
Valid License Headers
GPL Versions Summary
| Version | Year | Key Addition |
|---|---|---|
| GPLv1 | 1989 | Base copyleft: share-alike for modifications |
| GPLv2 | 1991 | "Liberty or death" clause (Section 7), clearer distribution terms |
| GPLv3 | 2007 | Anti-tivoization, explicit patent grants, compatibility provisions |
WordPress uses GPLv2 or later, meaning plugins can use GPLv2, GPLv3, or "GPLv2 or later".
For full license texts, see:
Show full SKILL.md (224 more words)Show less
License Compliance Checklist
When reviewing a plugin, verify:
- Main plugin file has a valid
License:header (e.g.,GPL-2.0-or-later,GPL-2.0+,GPLv2 or later) - Main plugin file has a
License URI:header pointing to the GPL text - If bundled libraries exist, each has a GPL-compatible license
- No "split licensing" (e.g., code GPL but premium features proprietary)
- No additional restrictions beyond what GPL allows
- No clauses restricting commercial use, modification, or redistribution
- No obfuscated code (violates the spirit of source code availability)
Valid License Headers for WordPress Plugins
License: GPL-2.0-or-later
License URI: https://www.gnu.org/licenses/gpl-2.0.htmlLicense: GPL-3.0-or-later
License URI: https://www.gnu.org/licenses/gpl-3.0.htmlLicense: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.htmlGPL-Compatible Licenses (Quick)
- Safe defaults: GPL-2.0-or-later, GPL-3.0-or-later.
- Commonly accepted permissive families: MIT/Expat, BSD, ISC, zlib, Boost.
- Conditional compatibility requires care: Apache-2.0 and MPL-2.0 (verify usage context).
- For full accepted and rejected identifiers, use gpl-compliance.md.
Common GPL Violations (Quick)
- Split licensing that restricts distributed code.
- Obfuscated or non-corresponding source distribution.
- Restrictive clauses (non-commercial, no-resale, forced backlink).
- Bundling GPL-incompatible libraries or assets.
Plugin Naming Rules (Guideline 17)
Use naming-rules.md for full trademark lists, slug blocks, and naming examples. Keep this inline checklist for quick screening.
Naming Checklist (Quick)
- Name is not a placeholder and has at least 5 alphanumeric characters.
- Header name and readme name match.
- Name is specific and function-related; avoid keyword stuffing.
- Trademark/project names appear only after connectors like
for,with,using,and. - No banned/discouraged terms or trademark portmanteaus.
- Slug is lowercase, hyphenated, <= 50 chars, and avoids blocked terms.
© gambitph, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 3 other files (references) in .cursor/skills/wp-plugin-directory-guidelines of gambitph/Stackable.
- SKILL.md
- references/gpl-compliance.md
- references/guideline-review-checklist.md
- references/naming-rules.md
Open the folder on GitHubat commit 5c13d80
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in gambitph/Stackable, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Wp Plugin Directory Guidelines next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wp Plugin Directory Guidelines this skillgambitph/Stackable | 350 | 1 repos | ~1.6k | Automated safety check: Pass | GPL-3.0 | |
| Paper to Chinese Patent DrafterYuan1z0825/nature-skills | 46k | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill | 105 | 1 repos | ~959 | Automated safety check: Pass | None | |
| Patent Examinegfodor/legal-skills | 393 | — | ~4.8k | Automated safety check: Pass | GPL-3.0 | |
| Patent Auditgfodor/legal-skills | 393 | — | ~2.9k | Automated safety check: Pass | GPL-3.0 | |
| Patent Workaroundgfodor/legal-skills | 393 | — | ~5.7k | Automated safety check: Pass | GPL-3.0 |
Similar skills
Paper To Cn Patent
snipp-zha/Paper-to-patent-Skill
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.
Patent Examine
gfodor/legal-skills
Iteratively examine and revise a draft U.S. An agent skill from gfodor/legal-skills.
Patent Audit
gfodor/legal-skills
Audit a draft U.S. An agent skill from gfodor/legal-skills.
Patent Workaround
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
Design Information Prep
SeanJ1ang/design-judge-skills
Extract evidence-grounded project facts from user-provided design attachments, identify missing information, and prepare the exact written fields required by supported design-award entry forms.
More from gambitph/Stackable
All 18 skills in this repoWp Block Development
gambitph/Stackable
A skill your agent uses when developing WordPress (Gutenberg) blocks: block.json metadata, registerblocktype(frommetadata), attributes/serialization, supports, dynamic rendering…
Wp Block Themes
gambitph/Stackable
A skill your agent uses when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style…
Wp Performance
gambitph/Stackable
A skill your agent uses when investigating or improving WordPress performance (backend-only agent): profiling and measurement (WP-CLI profile/doctor, Server-Timing, Query Monitor via REST headers)…
Wp Plugin Development
gambitph/Stackable
A skill your agent uses when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security…
Wp Project Triage
gambitph/Stackable
A skill your agent uses when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a…
Add Changelog
gambitph/Stackable
Adds or updates a WordPress plugin changelog entry in readme.txt from the project's Release Roadmap for a confirmed plugin version.
Related
Works with
Categories
Questions about Wp Plugin Directory Guidelines
What does Wp Plugin Directory Guidelines do?
A skill your agent uses when reviewing WordPress plugins for GPL compliance, checking license headers or compatibility, evaluating upsell/freemium/trialware patterns, validating plugin naming or…. Wp Plugin Directory Guidelines is an agent skill from gambitph/Stackable.org Plugin Directory guidelines — even if the user doesn't mention 'guidelines' explicitly.
When should I use Wp Plugin Directory Guidelines?
Wp Plugin Directory Guidelines fits situations like: reviewing WordPress plugins for GPL compliance; checking license headers; evaluating upsell/freemium/trialware patterns; validating plugin naming.
How do I install Wp Plugin Directory Guidelines in Claude Code?
Run `npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a claude-code`. Or copy the skill folder (.cursor/skills/wp-plugin-directory-guidelines in gambitph/Stackable) into .claude/skills/wp-plugin-directory-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install Wp Plugin Directory Guidelines in Codex?
Run `npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a codex`. Or copy the skill folder (.cursor/skills/wp-plugin-directory-guidelines in gambitph/Stackable) into .agents/skills/wp-plugin-directory-guidelines in your project. Codex loads it when a task matches its description.
Can I use Wp Plugin Directory Guidelines in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gambitph/Stackable --skill wp-plugin-directory-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wp-plugin-directory-guidelines, .gemini/skills/wp-plugin-directory-guidelines, .github/skills/wp-plugin-directory-guidelines and .opencode/skills/wp-plugin-directory-guidelines in your project.
What does Wp Plugin Directory Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: Wp Plugin Directory Guidelines is instructions for the agent only. Compatibility (from SKILL.md): Targets WordPress 7.0+ (PHP 7.4.0+)..
Does Wp Plugin Directory Guidelines access the network?
SKILL.md names 1 domain. In commands or code: gnu.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Wp Plugin Directory Guidelines safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Wp Plugin Directory Guidelines use?
Wp Plugin Directory Guidelines is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wp Plugin Directory Guidelines use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.
What are the alternatives to Wp Plugin Directory Guidelines?
Skills that share tags, products or a category with Wp Plugin Directory Guidelines: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 46k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 105 stars), Patent Examine (gfodor/legal-skills, 393 stars) and Patent Audit (gfodor/legal-skills, 393 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wp Plugin Directory Guidelines?
gambitph (a GitHub organization) maintains it in gambitph/Stackable, which has 350 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 7, 2026.
Source: gambitph/Stackable on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.