Agent skill

Best Practices

by MoizIbnYousaf in MoizIbnYousaf/ai-agent-skills

Transforms vague prompts into optimized Claude Code prompts.

MITAuto-check passedAgent Workflows

Install Best Practices

skills CLI
$ npx skills add MoizIbnYousaf/ai-agent-skills --skill best-practices -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MoizIbnYousaf/ai-agent-skills best-practices --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MoizIbnYousaf/ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/best-practices .claude/skills/best-practices && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
best-practices
GitHub stars
1.1k
Token cost
~4.2k tokens
SKILL.md length
1,200 words
Files
9 (incl. references)
Skills in repo
15
Repo updated
First seen
Licence
MIT

At a glance

Transforms vague prompts into optimized Claude Code prompts.

  • Works in 5 steps: Add Verification (Highest Priority) → Provide Specific Context → Add Constraints → …
  • Agent Workflows work in your project
  • SKILL.md covers Start Here, If "Transform directly", If "Build context first" and Transformation Workflow, plus 8 more sections
  • Calls claude

What it does

Best Practices is an agent skill from MoizIbnYousaf/ai-agent-skills. Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.

Its SKILL.md is about 4.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `agents/best-practices-referencer.md`, `agents/codebase-context-builder.md` and `agents/task-intent-analyzer.md`).

It sits in Agent Workflows. The repository describes itself as: Universal skill installer and package manager for AI coding agents. One command, 12+ runtimes. npx ai-agent-skills. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “Use the best-practices skill to transform vague prompts into optimized Claude Code prompts”
  • “/best-practices”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Add Verification (Highest Priority)
  2. Provide Specific Context
  3. Add Constraints
  4. Structure Complex Tasks in Phases
  5. Include Rich Content

What it can do on your machine

Read from SKILL.md and the folder at commit 6d95c78. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • claude

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • code.claude.com
    • docs.anthropic.com
    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Best Practices loads about 4.2k tokens when it runs, and up to ~29k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 1,200 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~4.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~29k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MoizIbnYousaf/ai-agent-skills at commit 6d95c78, republished under its MIT licence (© MoizIbnYousaf). 1,200 words, ~4,206 tokens.

Download SKILL.mdSave it as .claude/skills/best-practices/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.
name
best-practices
description
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
version
4.1.0

Best Practices — Prompt Transformer

Transform prompts by adding what Claude needs to succeed.

Start Here

Based on user's request:

User provides a prompt to transform: → Ask using AskUserQuestion:

  • Question: "How should I improve this prompt?"
  • Header: "Mode"
  • Options:
    1. Transform directly — "I'll apply best practices and output an improved version"
    2. Build context first — "I'll gather codebase context and intent analysis first"

User asks to learn/understand: → Show the 5 Transformation Principles section

User asks for examples: → Link to references/before-after-examples.md

User asks to evaluate a prompt: → Use the Success Criteria eval rubric at the end of this document


If "Transform directly"

Apply the 5 principles below and output the improved prompt immediately.

If "Build context first"

Launch 3 parallel agents to gather context:

Run these agents IN PARALLEL using the Task tool:

- Task task-intent-analyzer("[user's prompt]")
- Task best-practices-referencer("[user's prompt]")
- Task codebase-context-builder("[user's prompt]")
What Each Agent Returns
AgentMissionReturns
task-intent-analyzerUnderstand what user is trying to doTask type, gaps, edge cases, transformation guidance
best-practices-referencerFind relevant patterns from references/Matching examples, anti-patterns to avoid, transformation rules
codebase-context-builderExplore THIS codebaseSpecific file paths, similar implementations, conventions
After Agents Return
  1. Synthesize findings — Combine intent + best practices + codebase context
  2. Apply matching patterns — Use examples from best-practices-referencer as templates
  3. Ground in codebase — Add specific file paths from codebase-context-builder
  4. Transform the prompt — Apply the 5 principles with all gathered context
  5. Output — Show improved prompt with before/after comparison
Agent Definitions

The agents are defined in agents/:

  • agents/task-intent-analyzer.md — Analyzes intent, gaps, and edge cases
  • agents/best-practices-referencer.md — Finds relevant examples and patterns from references/
  • agents/codebase-context-builder.md — Explores codebase for files and conventions

Transformation Workflow

When transforming (after mode selection):

  1. Identify what's missing — Check against the 5 principles below
  2. Add missing elements — Verification, context, constraints, phases, rich content
  3. Output the improved prompt — In a code block, ready to copy-paste
  4. Show what changed — Brief comparison of before/after

The 5 Transformation Principles

Apply these in order of priority:

1. Add Verification (Highest Priority)

The single highest-leverage improvement. Claude performs dramatically better when it can verify its own work.

MissingAdd
No success criteriaTest cases with expected inputs/outputs
UI changes"take screenshot and compare to design"
Bug fixes"write a failing test, then fix it"
Build issues"verify the build succeeds after fixing"
Refactoring"run the test suite after each change"
No root cause enforcement"address root cause, don't suppress error"
No verification report"summarize what you ran and what passed"
BEFORE: "implement email validation"
AFTER:  "write a validateEmail function. test cases: user@example.com → true,
         invalid → false, user@.com → false. run the tests after implementing"
BEFORE: "fix the API error"
AFTER:  "the /api/orders endpoint returns 500 for large orders. check
         OrderService.ts for the error. address the root cause, don't suppress
         the error. after fixing, run the test suite and summarize what passed
         and what you verified."
2. Provide Specific Context

Replace vague references with precise locations and details.

VagueSpecific
"the code"src/auth/login.ts
"the bug""users report X happens when Y"
"the API""the /api/users endpoint in routes.ts"
"that function"processPayment() on line 142

Four ways to add context:

StrategyExample
Scope the task"write a test for foo.py covering the edge case where user is logged out. avoid mocks."
Point to sources"look through ExecutionFactory's git history and summarize how its API evolved"
Reference patterns"look at HotDogWidget.php and follow that pattern for the calendar widget"
Describe symptoms"users report login fails after session timeout. check src/auth/, especially token refresh"

Respect Project CLAUDE.md:

If the project has a CLAUDE.md, the transformed prompt should:

  • Not contradict project conventions
  • Reference project-specific patterns when relevant
  • Note any project constraints that apply
BEFORE: "add a new API endpoint"
AFTER:  "add a GET /api/products endpoint. check CLAUDE.md for API conventions
         in this project. follow the pattern in routes/users.ts. run the API
         tests after implementing."
BEFORE: "fix the login bug"
AFTER:  "users report login fails after session timeout. check the auth flow
         in src/auth/, especially token refresh. write a failing test that
         reproduces the issue, then fix it"
3. Add Constraints

Tell Claude what NOT to do. Prevents over-engineering and unwanted changes.

Constraint TypeExamples
Dependencies"no new libraries", "only use existing deps"
Testing"avoid mocks", "use real database in tests"
Scope"don't refactor unrelated code", "only touch auth module"
Approach"address root cause, don't suppress error", "keep backward compat"
Patterns"follow existing codebase conventions", "match the style in utils.ts"
BEFORE: "add a calendar widget"
AFTER:  "implement a calendar widget with month selection and year pagination.
         follow the pattern in HotDogWidget.php. build from scratch without
         libraries other than the ones already used in the codebase"
4. Structure Complex Tasks in Phases

For larger tasks, separate exploration from implementation.

The 4-Phase Pattern:

Phase 1: EXPLORE
"read src/auth/ and understand how we handle sessions and login.
 also look at how we manage environment variables for secrets."

Phase 2: PLAN
"I want to add Google OAuth. What files need to change?
 What's the session flow? Create a plan."

Phase 3: IMPLEMENT
"implement the OAuth flow from your plan. write tests for the
 callback handler, run the test suite and fix any failures."

Phase 4: COMMIT
"commit with a descriptive message and open a PR"

When to use phases:

  • Uncertain about the approach
  • Change modifies multiple files
  • Unfamiliar with the code being modified

Skip phases when:

  • Could describe the diff in one sentence
  • Fixing a typo, adding a log line, renaming a variable
BEFORE: "add OAuth"
AFTER:  "read src/auth/ and understand current session handling. create a plan
         for adding OAuth. then implement following the plan. write tests and
         verify they pass"
5. Include Rich Content

Provide supporting materials that Claude can use directly.

Content TypeHow to Provide
FilesUse @filename to reference files
ImagesPaste screenshots directly
ErrorsPaste actual error messages, not descriptions
LogsPipe with cat error.log | claude
URLsLink to relevant documentation
BEFORE: "make the dashboard look better"
AFTER:  "[paste screenshot] implement this design for the dashboard.
         take a screenshot of the result and compare it to the original.
         list any differences and fix them. ensure responsive behavior
         at 768px and 1024px breakpoints"
BEFORE: "the build is failing"
AFTER:  "the build fails with this error: [paste actual error]. fix it
         and verify the build succeeds. address the root cause, don't
         suppress the error"

Output Format

When transforming a prompt, output:

markdown
**Original:** [their prompt]

**Improved:**

[transformed prompt in code block]


**Added:**
- [what was missing and added]
- [another improvement]
- [etc.]

Quick Transformation Examples

Bug Fix
BEFORE: "fix the login bug"

AFTER: "users report login fails after session timeout. check the auth flow
in src/auth/, especially token refresh. write a failing test that reproduces
the issue, then fix it. verify by running the auth test suite."

ADDED: symptom, location, verification (failing test), success criteria
Feature Implementation
BEFORE: "add a search feature"

AFTER: "implement search for the products page. look at how filtering works
in ProductList.tsx for the pattern. search should filter by name and category.
add tests for: empty query returns all, partial match works, no results shows
message. no external search libraries."

ADDED: location, reference pattern, specific behavior, test cases, constraint
Refactoring
BEFORE: "make the code better"

AFTER: "refactor utils.js to use ES2024 features while maintaining the same
behavior. specifically: convert callbacks to async/await, use optional
chaining, add proper TypeScript types. run the existing test suite after
each change to ensure nothing breaks."

ADDED: specific changes, constraint (same behavior), verification after each step
Testing
BEFORE: "add tests for foo.py"

AFTER: "write tests for foo.py covering the edge case where the user is
logged out. avoid mocks. use the existing test patterns in tests/. test
cases: logged_out_user returns 401, expired_session redirects to login,
invalid_token raises AuthError."

ADDED: specific edge case, constraint (no mocks), pattern reference, test cases
Debugging
BEFORE: "the API is slow"

AFTER: "the /api/orders endpoint takes 3+ seconds. profile the database
queries in OrderService.ts. look for N+1 queries or missing indexes.
fix the performance issue and verify response time is under 500ms."

ADDED: specific endpoint, location, what to look for, measurable success criteria
UI Changes
BEFORE: "fix the button styling"

AFTER: "[paste screenshot of design] update the primary button to match this
design. check Button.tsx and the theme in tailwind.config.js. take a
screenshot after changes and compare to the design. list any differences."

ADDED: design reference, file locations, visual verification
Exploration
BEFORE: "how does auth work?"

AFTER: "read src/auth/ and explain how authentication works in this codebase.
cover: how sessions are created, how tokens are refreshed, where secrets
are stored. summarize in a markdown doc."

ADDED: specific files, specific questions to answer, output format
Migration
BEFORE: "upgrade to React 18"

AFTER: "migrate from React 17 to React 18. first, read the migration guide
at [URL]. then identify all components using deprecated APIs. update one
component at a time, running tests after each. don't change unrelated code."

ADDED: phased approach, reference docs, incremental verification, scope constraint
With Verification Report
BEFORE: "fix the API error"

AFTER: "the /api/orders endpoint returns 500 for large orders. check
OrderService.ts for the error. address the root cause, don't suppress
the error. after fixing, run the test suite and summarize what passed
and what you verified."

ADDED: symptom, location, root cause enforcement, verification report

Show full SKILL.md (488 more words)Show less

Transformation Checklist

Before outputting, verify the improved prompt has:

  • Verification — How to know it worked (tests, screenshot, output)
  • Location — Specific files, functions, or areas
  • Constraints — What NOT to do
  • Single task — Not compound (split if needed)
  • Phases — If complex, structured as explore → plan → implement
  • Root cause — For bugs: "address root cause, don't suppress"
  • CLAUDE.md — Respect project conventions if they exist

Quick Prompt Quality Check

Rate the prompt against these dimensions:

Dimension0 (Missing)1 (Partial)2 (Complete)
VerificationNone"test it"Specific test cases + report
Location"the code""auth module"src/auth/login.ts:42
ConstraintsNoneImplied"avoid X, no Y, root cause only"
ScopeVaguePartialSingle clear task

Quick assessment:

  • 0-3: Needs significant work
  • 4-5: Needs some improvements
  • 6-8: Good, minor tweaks

Fallback: If Still Too Vague

If user chose "Transform directly" but the prompt lacks enough context, ask one natural question:

"What would Claude need to know to do this well?"

Don't interrogate — one question is enough. Transform with what you learn.


Common Anti-Patterns to Fix

Anti-PatternProblemFix
"fix the bug"No symptom, no locationAdd what users report + where to look
"add tests"No scope, no casesSpecify edge cases + test patterns
"make it better"No criteria for "better"Define specific improvements
"implement X"No verificationAdd test cases or success criteria
"update the code"No constraintsAdd what to preserve, what to avoid

Success Criteria — Prompt Quality Eval

A well-transformed prompt passes these checks:

Principle 1: Verification ✅
CheckPassFail
Has success criteria"run tests", "screenshot matches"Nothing
Measurable outcome"response < 500ms""make it faster"
Self-verifiableClaude can check its own workRequires human judgment
Root cause enforced"don't suppress error"Silent about approach
Principle 2: Specificity ✅
CheckPassFail
File locationssrc/auth/login.ts"the auth code"
Function/class namesprocessPayment()"that function"
Line numbers (if relevant):42"somewhere in there"
CLAUDE.md respected"check project conventions"Ignores project rules
Principle 3: Constraints ✅
CheckPassFail
What NOT to do"avoid mocks", "no new deps"Open-ended
Scope boundaries"only touch auth module"Unlimited scope
Pattern to follow"match UserService.ts style"No reference
Principle 4: Structure ✅
CheckPassFail
Single taskOne clear objectiveMultiple goals
Phased (if complex)"explore → plan → implement"Jump straight to code
Appropriate depthMatches task complexityOver/under-specified
Principle 5: Rich Content ✅
CheckPassFail
Actual errorsPasted error message"it's broken"
Screenshots (UI)Image attached"the button looks wrong"
File references@filename or path"that file"
Overall Quality Score
ScoreMeaningPrinciples Passed
⭐⭐⭐⭐⭐ExcellentAll 5
⭐⭐⭐⭐Good4 of 5
⭐⭐⭐Acceptable3 of 5
⭐⭐Needs work2 of 5
⭐Poor1 or 0

Target: Every transformed prompt should score ⭐⭐⭐⭐ or ⭐⭐⭐⭐⭐


Reference Files

For more examples and patterns:


Sources

© MoizIbnYousaf, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 8 other files (references) in skills/best-practices of MoizIbnYousaf/ai-agent-skills.

  • SKILL.md
  • agents/best-practices-referencer.md
  • agents/codebase-context-builder.md
  • agents/task-intent-analyzer.md
  • references/anti-patterns.md
  • references/before-after-examples.md
  • references/best-practices-guide.md
  • references/common-workflows.md
  • references/prompt-patterns.md

Open the folder on GitHubat commit 6d95c78

Compare with similar skills

Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Best Practices compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Best Practices this skillMoizIbnYousaf/ai-agent-skills1.1k—~4.2kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from MoizIbnYousaf/ai-agent-skills

All 15 skills in this repo
  • Database Design

    MoizIbnYousaf/ai-agent-skills

    Database schema design, optimization, and migration patterns for PostgreSQL, MySQL, and NoSQL databases.

    1.1k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • LLM Application Dev

    MoizIbnYousaf/ai-agent-skills

    Building applications with Large Language Models - prompt engineering, RAG patterns, and LLM integration.

    1.1k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed
  • Audit Library Health

    MoizIbnYousaf/ai-agent-skills

    A skill your agent uses when checking the overall health of a skills library.

    1.1k GitHub stars~518 tokensUpdated 18 days ago
    Auto-check passed
  • Backend Development

    MoizIbnYousaf/ai-agent-skills

    Backend API design, database architecture, microservices patterns, and test-driven development.

    1.1k GitHub stars~853 tokensUpdated 18 days ago
    Auto-check passed
  • Browse And Evaluate

    MoizIbnYousaf/ai-agent-skills

    A skill your agent uses when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing.

    1.1k GitHub stars~453 tokensUpdated 18 days ago
    Auto-check passed
  • Code Documentation

    MoizIbnYousaf/ai-agent-skills

    Writing effective code documentation - API docs, README files, inline comments, and technical guides.

    1.1k GitHub stars~1.4k tokensUpdated 18 days ago
    Auto-check passed

Categories

Questions about Best Practices

What does Best Practices do?

Transforms vague prompts into optimized Claude Code prompts. Best Practices is an agent skill from MoizIbnYousaf/ai-agent-skills. Transforms vague prompts into optimized Claude Code prompts.

When should I use Best Practices?

Best Practices fits situations like: agent Workflows work in your project.

How do I install Best Practices in Claude Code?

Run `npx skills add MoizIbnYousaf/ai-agent-skills --skill best-practices -a claude-code`. Or copy the skill folder (skills/best-practices in MoizIbnYousaf/ai-agent-skills) into .claude/skills/best-practices in your project. Claude Code loads it when a task matches its description.

How do I install Best Practices in Codex?

Run `npx skills add MoizIbnYousaf/ai-agent-skills --skill best-practices -a codex`. Or copy the skill folder (skills/best-practices in MoizIbnYousaf/ai-agent-skills) into .agents/skills/best-practices in your project. Codex loads it when a task matches its description.

Can I use Best Practices in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MoizIbnYousaf/ai-agent-skills --skill best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/best-practices, .gemini/skills/best-practices, .github/skills/best-practices and .opencode/skills/best-practices in your project.

What does Best Practices need to run?

Going by SKILL.md and its folder, Best Practices needs the command-line tools its instructions call (claude).

Does Best Practices access the network?

SKILL.md names 3 domains. As links in the text: code.claude.com, docs.anthropic.com and github.com. This is read from the text; nothing was executed.

Is Best Practices safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Best Practices use?

Best Practices is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Best Practices use?

About 4.2k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 25k tokens, read only when the agent opens those files.

What are the alternatives to Best Practices?

Skills that share tags, products or a category with Best Practices: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Best Practices?

MoizIbnYousaf (a GitHub user) maintains it in MoizIbnYousaf/ai-agent-skills, which has 1,149 GitHub stars. The repository holds 15 skills in this directory. The repository was last updated on September 21, 2026.

Source: MoizIbnYousaf/ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.