From file to useful result
How to ask with this skill installed
Installing the skill gives your AI a method. Your request still has to provide the case-specific facts, constraints and expected output.
Describe the decision or deliverable, not just the topic.
Add source material, audience, limits and known facts.
Set format, quality criteria and checks.
Mistakes to avoid
| Mistake | Correct | |---------|---------| | pluginZipFile / themeZipFile | pluginData / themeData | | "step": "cli" | "step": "wp-cli" | | Flat object as writeFiles.filesTree | Must be a literal:directory or git:directory resource | | Path separators in files keys | Use nested objects for subdirectories | | runPHP without wp-load.php | Always require '/wordpress/wp-load.php'; for WP functions | | Invented top-level keys | Only documented keys work — schema rejects unknown properties | | Inventing proxy URLs for GitHub | Use git:directory resource type | | Omitting refType with branch/tag ref | Required — only "HEAD" works without it | | Resource references in literal:directory files values | Values must be plain strings (content) or objects (subdirectories) — never resource refs | | features.debug or other invented feature keys | features only supports networking and intl — use constants: { "WP_DEBUG": true } for debug mode | | require wp-load.php in mu-plugin code | Only needed in runPHP steps — mu-plugins already run within WordPress | | Schema URL with .org domain | Must be playground.wordpress.net, not playground.wordpress.org |