acf
ACF integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACF data.
32
26%
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/acf/SKILL.mdQuality
Discovery
17%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 description is too vague and relies heavily on the unexplained acronym 'ACF' without providing context (presumably Advanced Custom Fields for WordPress). The actions listed are generic ('manage data, records, automate workflows') and the trigger clause is circular. It would be very difficult for Claude to distinguish this skill from other data management skills.
Suggestions
Expand the acronym ACF (Advanced Custom Fields) and specify the platform (WordPress) to establish context and improve distinctiveness.
Replace vague actions with concrete ones, e.g., 'Create and configure ACF field groups, query custom field values, update post meta, register repeater fields.'
Improve trigger terms by adding natural keywords users would say: 'Use when working with WordPress custom fields, ACF field groups, post meta, repeater fields, flexible content, or .php files referencing get_field/update_field.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'manage data, records, and automate workflows' without specifying concrete actions. It doesn't explain what ACF is or what specific operations can be performed (e.g., create fields, query post meta, register field groups). | 1 / 3 |
Completeness | It has a basic 'what' (manage data, records, automate workflows) and a 'Use when' clause, but both are extremely vague. The 'when' clause ('when the user wants to interact with ACF data') is essentially a tautology that doesn't provide meaningful trigger guidance. | 2 / 3 |
Trigger Term Quality | The only trigger term is 'ACF data,' which is a technical acronym (Advanced Custom Fields) that many users might not use. It lacks natural keywords like 'custom fields,' 'WordPress fields,' 'post meta,' 'field groups,' or 'ACF plugin.' | 1 / 3 |
Distinctiveness Conflict Risk | 'Manage data, records, and automate workflows' is extremely generic and could conflict with database skills, CRM skills, spreadsheet skills, or any data management tool. Without clarifying that ACF refers to Advanced Custom Fields in WordPress, the description lacks a clear niche. | 1 / 3 |
Total | 5 / 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 is primarily a generic Membrane CLI integration template with minimal ACF-specific content. The opening explanation of what ACF is wastes tokens on knowledge Claude already has, and the 'Popular actions' section provides no actual ACF actions or examples. The bulk of the content covers Membrane authentication and CLI usage patterns that are not unique to ACF.
Suggestions
Remove the introductory paragraph explaining what ACF is and replace it with ACF-specific action examples (e.g., creating field groups, reading custom fields, updating entries) with concrete input/output JSON.
Populate the 'Popular actions' section with actual ACF action names, their parameters, and example invocations rather than just a discovery command.
Extract the generic Membrane CLI setup, authentication, and proxy documentation into a shared reference file and link to it, keeping only ACF-specific content inline.
Add ACF-specific workflow examples with validation steps, such as verifying a field group was created correctly or checking that custom field data was saved as expected.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose with unnecessary explanations Claude already knows (e.g., 'ACF is a WordPress plugin that allows developers to add custom fields...', 'It simplifies content management...'). The Membrane CLI setup, authentication flow, and proxy request documentation are generic boilerplate not specific to ACF, consuming significant tokens without ACF-specific value. | 1 / 3 |
Actionability | The skill provides concrete CLI commands for authentication, connection setup, action discovery, and proxy requests. However, there are no ACF-specific examples (e.g., creating a field group, retrieving custom field values, updating entries), making the guidance generic rather than truly actionable for ACF workflows. | 2 / 3 |
Workflow Clarity | The connection setup workflow has a reasonable sequence with state-based branching (READY, CLIENT_ACTION_REQUIRED, etc.), but there are no validation checkpoints for actual ACF operations. The 'Popular actions' section is empty of actual actions, and there's no error recovery guidance for ACF-specific operations. | 2 / 3 |
Progressive Disclosure | The content has some structure with headers and sections, but it's largely monolithic — the Membrane CLI generic documentation (authentication, proxy requests, best practices) is inlined rather than referenced from a shared location. No bundle files are provided, and the ACF overview section is skeletal while generic Membrane content dominates. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- membranedev/application-skills
- Commit
f484c82
- 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.