acf
ACF integration. Manage data, records, and automate workflows. Use when the user wants to interact with ACF data.
66
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
52%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description follows the correct structure with a 'Use when...' clause, but suffers from vague terminology and unexplained acronyms. 'ACF' is never defined, making it unclear what system this integrates with, and the actions described are too generic to help Claude distinguish this skill from other data management tools.
Suggestions
Define what ACF stands for and briefly describe the system (e.g., 'ACF (Advanced Custom Fields) WordPress plugin integration' or whatever ACF refers to)
Add specific trigger terms users would naturally say, such as the full name of ACF, specific field types, or common tasks like 'custom fields', 'WordPress fields', 'field groups'
Replace generic actions with concrete capabilities (e.g., 'create field groups, query custom field values, update post meta' instead of 'manage data, records')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (ACF) and mentions some actions ('Manage data, records, and automate workflows'), but these are fairly generic and not comprehensive - doesn't specify what kinds of data, records, or workflows. | 2 / 3 |
Completeness | Has both 'what' (manage data, records, automate workflows) and 'when' (explicit 'Use when the user wants to interact with ACF data'), though both parts are somewhat vague. | 3 / 3 |
Trigger Term Quality | Uses 'ACF' which is technical jargon without explanation, and 'data', 'records', 'workflows' are overly generic terms. Missing natural variations users might say (e.g., what ACF stands for, specific use cases). | 1 / 3 |
Distinctiveness Conflict Risk | 'ACF' provides some distinctiveness as a specific system, but 'data', 'records', and 'workflows' are generic enough to potentially overlap with many other data management or automation skills. | 2 / 3 |
Total | 8 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable CLI commands for ACF integration via Membrane, with good coverage of common operations and proxy requests. However, it wastes tokens explaining what ACF is, lacks error handling/validation guidance in workflows, and could benefit from better organization with external references for detailed content like the proxy options table.
Suggestions
Remove the opening paragraph explaining what ACF is - Claude already knows this
Add validation checkpoints and error handling guidance (e.g., 'If connection fails, check X' or 'Verify connection with membrane connection list before proceeding')
Move the proxy request options table to a separate REFERENCE.md file and link to it
Restructure the workflow to include a decision point: check for existing connections FIRST, then create if needed
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The opening paragraph explains what ACF is, which Claude already knows. The Membrane CLI setup instructions are necessary but could be tighter. Some sections like 'ACF Overview' with bullet points add little value. | 2 / 3 |
Actionability | Provides fully executable CLI commands throughout - installation, login, connection creation, action discovery, and proxy requests are all copy-paste ready with clear flag documentation. | 3 / 3 |
Workflow Clarity | Steps are listed for setup and connection but lack validation checkpoints. No guidance on what to do if commands fail, and the 'Getting list of existing connections' section is awkwardly placed mid-workflow rather than as a decision point. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in one file. The proxy request options table and best practices could be separate references. Links to official docs are provided but no internal file references for advanced topics. | 2 / 3 |
Total | 9 / 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 | |
- 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.