agentsclimarketplace

Wp acf blocks

Skill phucbm/skills/skills/wordpress/wp-acf-blocks

Claude Plugin - Personal knowledge base for Claude Code — patterns and integrations across projects

Install
npx -y skills add phucbm/skills --skill wp-acf-blocks

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scaffold, revise and manage custom ACF Gutenberg blocks for WordPress with Tailwind CSS. Use when the user wants to create a new block, revise/audit blocks, or set up a WordPress blocks project.

SKILL.md

1.9 KB, as published. Nobody here has run it

Read @/knowledge/overview.md, then determine which sub-skill to invoke based on the user's request:

  • /wp-acf-blocks:setup — set up a new theme with the full directory structure and mu-plugins
  • /wp-acf-blocks:plan-block — discuss a block's requirements and create a GitHub issue with structured breakdown
  • /wp-acf-blocks:add-block — scaffold one or more blocks from GitHub issues, markdown brief, or interactive prompts
  • /wp-acf-blocks:revise-block — fast structural audit (files, wrappers, timestamps); accepts block slugs as args
  • /wp-acf-blocks:revise-block-deep — structural audit + AI content quality review; accepts block slugs as args

For general questions about conventions, PHP patterns, ACF fields, Tailwind build, or TypeScript setup, read the relevant knowledge files directly:

Gives 0 of the 12 instructions most css styling skills give

Counted across 586 of the 596 authors here whose files we hold, read 2026-08-06

  • avoid excessive centered layoutsin 55 of 586, across 12 files
  • bundle code into single HTML filein 54 of 586, across 14 files
  • Respect prefers-reduced-motion user settingsin 52 of 586, across 35 files
  • avoid purple gradientsin 51 of 586, across 11 files
  • avoid uniform rounded cornersin 51 of 586, across 11 files
  • avoid Inter fontin 51 of 586, across 11 files
  • edit generated files to develop artifactin 50 of 586, across 10 files
  • animate only transform and opacity propertiesin 43 of 586
  • Make touch targets at least 44x44 pixelsin 41 of 586, across 15 files
  • Ensure minimum color contrast of 4.5:1in 39 of 586, across 10 files
  • use tailwind cssin 39 of 586, across 24 files
  • Use SVG icons instead of emojisin 38 of 586, across 11 files

Said here and by no other author read

  • Read the overview document first
  • Determine the correct sub-skill from the user request
  • Invoke the setup sub-skill for new themes
  • Invoke the plan-block sub-skill to create a GitHub issue
  • Invoke the add-block sub-skill to scaffold blocks
  • Invoke the revise-block sub-skill for a fast audit

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.