acf-local-json
Generate Advanced Custom Fields (ACF) Local JSON configurations for WordPress from visual designs or HTML structures. Use when creating ACF field groups, converting designs to ACF schemas, building WordPress custom fields from mockups, or when working with ACF Pro Local JSON format. Supports flexible content, repeaters, clone fields, and all ACF field types.
59
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/local-json-acf/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines a specific niche (ACF Local JSON generation for WordPress), provides concrete actions and supported features, and includes an explicit 'Use when' clause with natural trigger terms. It follows third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: generating ACF Local JSON configurations, converting visual designs/HTML to ACF schemas, building custom fields from mockups. Also specifies supported field types: flexible content, repeaters, clone fields, and all ACF field types. | 3 / 3 |
Completeness | Clearly answers both 'what' (generate ACF Local JSON configurations from visual designs or HTML structures) and 'when' (explicit 'Use when' clause covering creating field groups, converting designs to schemas, building custom fields from mockups, or working with ACF Pro Local JSON format). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a WordPress developer would use: 'ACF', 'Advanced Custom Fields', 'Local JSON', 'field groups', 'ACF schemas', 'WordPress custom fields', 'mockups', 'ACF Pro', 'flexible content', 'repeaters', 'clone fields'. These are all terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche targeting ACF Local JSON for WordPress specifically. The combination of ACF, Local JSON, WordPress, and design-to-schema conversion creates a very clear and unique trigger profile unlikely to conflict with general WordPress or general JSON skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive ACF JSON reference material but suffers from significant verbosity—most of the JSON structure templates represent knowledge Claude already has about ACF Pro's Local JSON format. The workflow is high-level without concrete validation steps, and the bulk of the content (field patterns, location rules) would be better placed in reference files rather than inline. The field type detection mapping tables add some value but are over-explained.
Suggestions
Move the JSON structure templates (basic field, repeater, flexible content, image, location rules) into a separate reference file and keep only a minimal example in the main skill body.
Replace the vague 'Validate Structure' step with concrete validation criteria: required keys checklist, key uniqueness verification, proper parent references in sub_fields, and valid JSON syntax check.
Remove obvious mappings from the field type detection section (e.g., `<img>` → image) and keep only non-obvious or ACF-specific decisions like when to use `flexible_content` vs `repeater`.
Provide the complete JSON output for the example workflow instead of just the analysis outline, so Claude has a concrete end-to-end reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with extensive JSON templates that Claude already knows how to generate. ACF field structure patterns, basic field definitions, image field properties, and location rule patterns are all well-documented public knowledge that Claude possesses. The field type detection guidelines section also over-explains obvious mappings (e.g., `<img>` → image field). | 1 / 3 |
Actionability | The JSON templates are concrete and copy-paste ready, which is good. However, the workflow itself is vague ('Analyze Input', 'Identify Components') without executable steps, and the example workflow at the end only shows the analysis outline without the actual generated output. Key generation mentions 'random_hash' but doesn't specify how to generate one. | 2 / 3 |
Workflow Clarity | The core workflow lists 5 steps but lacks validation checkpoints. Step 5 says 'Validate Structure' but provides no concrete validation method or criteria. There's no feedback loop for error recovery—if the JSON is malformed or keys conflict, there's no guidance on detection or correction. For a skill that generates JSON configurations, missing validation caps this at 2. | 2 / 3 |
Progressive Disclosure | The Advanced Features section appropriately references external files for clone fields, relationships, etc. However, the main body contains ~200 lines of JSON templates that could be split into a reference file, keeping the SKILL.md as a concise overview. The inline content is too heavy for what should be an overview document. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- josecortezz25/local-json-acf-skill
- Commit
f42aba1
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.