agentsclimarketplace

Init

Skill bromso/metapowers/plugins/metapowers/skills/init

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill init

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

One thing to look at

  • 1 stars1 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

Initialize a .metapowers/ directory and configure active domains for a project

SKILL.md

1.8 KB, 398 tokens by cl100k_base, as published. Nobody here has run it

Init

Initialize the .metapowers/ directory for the current project. Set up the project configuration and choose which domains to activate.

Prerequisites

None — this is typically the first Metapowers command you run in a new project.

Process

  1. Check if .metapowers/ already exists:

    • If it exists, read .metapowers/config.md and show current configuration
    • Ask if the user wants to update the configuration
    • If it doesn't exist, proceed with initialization

  2. Ask the user:

    • What is the project name?
    • Which domains will you use? Present the full list:
      • Design (component design with Figma integration)
      • Research (Double Diamond discovery and validation)
      • Development (plan, build, test, debug, review, ship)
      • Marketing (RACE Framework campaigns)
      • Branding (brand creation and compliance)
      • Accessibility (WCAG-EM audits)
      • Project Management (Scrum workflow)
      • Coaching (domain-specific mentorship)
      • Leadership (team development and management)
      • Legal (contracts, compliance, governance)

  3. Create the directory structure:

    • Create .metapowers/ root directory
    • Create subdirectories for each selected domain
    • Create .metapowers/reports/ for cross-domain reports

  4. Write the project configuration:

    • Write .metapowers/config.md with:
      • Project name
      • Active domains
      • Date initialized
      • Notes or goals (if the user provided any)

  5. Suggest next steps:

    • Based on selected domains, recommend which to start with
    • Provide the first command to run

Output

The project configuration written to .metapowers/config.md. Present the initialized structure and suggested next steps to the user.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 398 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

  • Ask one question at a timein 29 of 999, across 28 files
  • Detect the package manager from lockfilesin 28 of 999, across 9 files
  • Present findings to the userin 26 of 999, across 5 files
  • Explore current repo statein 24 of 999, across 3 files
  • Update the agent skills block in place if it existsin 24 of 999, across 3 files
  • Install husky lint-staged and prettierin 23 of 999, across 4 files
  • Create the lintstagedrc filein 22 of 999, across 3 files
  • Commit all changed filesin 22 of 999, across 3 files
  • Run lint-staged to verify it worksin 22 of 999, across 3 files
  • Create the husky pre-commit filein 21 of 999, across 2 files
  • Create a prettierrc file if missingin 21 of 999, across 2 files
  • Initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

  • create subdirectories for each selected domain
  • create a reports subdirectory

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,984. 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.