Agents Standards & Skills

Reuse coding-agent standards, writing guidance, and task workflows across supported assistants.

Source repo
scarletkc/agents
Stars
★ 227
Last updated
6d ago
License
Apache-2.0
Primary language
Python

At a glance

How it runs
Agent plugin / skillCLI
Works with
Universal · cross-platformCodex · Claude Code
Cost
Free, no paid service needed
Setup effort
Low · running in minutes
You'll need
GitHub CLI or npx skills CLIShell / CLINetwork accessLocal filesystem
Typical use
A developer using both Codex CLI and Claude Code wants the assistants to follow the same baseline collaboration and coding rules.
Not a fit if
  • Teams wanting a self-contained agent runtime
  • Users of assistants other than Codex CLI and Claude Code
  • Teams seeking a hosted service or model API
Source review
73/100 · Some gaps

What does this agent do, and when should you use it?

This repository is a collection of shared standards and reusable skills for AI coding assistants, not a standalone agent application. Its main components are a project-level AGENTS.md, a separate user/AGENTS.md for personal collaboration preferences, and a skills/ tree whose packages use the SKILL.md format. The listed skills cover planning, change scoping, product and UX writing, marketing copy, worktree-based PR preparation, and delegation to Codex CLI, Antigravity CLI, or Grok Build. Users can copy the base guidelines into a repository or install selected skills through GitHub CLI or the skills CLI for assistants such as Codex CLI and Claude Code. Its deliverables are Markdown instructions and supporting skill resources; a Python packaging script can also produce upload-ready ZIP archives. It fits developers and teams seeking consistent behavior across coding assistants, but it does not provide its own hosted service, model API, or agent execution engine.

The repository supplies project-agnostic rules in AGENTS.md, keeps user-level collaboration preferences in user/AGENTS.md, and defines reusable packages under skills/<skill>/SKILL.md. A compatible coding assistant reads those files and follows the selected workflow for guided planning, documentation or copywriting, scoped changes, worktree PR preparation, or delegation to Codex CLI, Antigravity CLI, and Grok Build. gh skill install scarletkc/agents and npx skills add scarletkc/agents browse and install skills, with supported options for selecting one skill and a target assistant. python scripts/package_skill.py <skill> writes dist/<skill>.zip with SKILL.md and its supporting files at the archive root while excluding root-level evals/ and local build artifacts. After edits to the shared task runtime, python scripts/sync_agent_runtime.py updates the bundled runtime copies carried by the CLI skills.

  1. A developer using both Codex CLI and Claude Code wants the assistants to follow the same baseline collaboration and coding rules.
  2. A team maintaining several repositories wants to reuse a base AGENTS.md while prepending structure, commands, and domain notes for each project.
  3. A user wants one bounded workflow, such as scoped-change for limiting an edit or ask-to-plan for turning a rough idea into an actionable plan.
  4. A product or technical writer needs to choose between the compact product-writing guide and the more prescriptive ux-writing rules.
  5. A skill maintainer needs an upload-ready ZIP containing SKILL.md and its supporting resources for a web application.
  6. A developer already working with Codex CLI, Antigravity CLI, or Grok Build wants a dedicated delegation workflow for that command-line product.

How do you install or deploy this agent?

You need a shell, network access, and permission to write to the destination skill directory. No model API credential is documented as a repository requirement. To browse interactively and install for the current Codex user with GitHub CLI, run gh skill install scarletkc/agents --agent codex --scope user. For a non-interactive single-skill installation, run gh skill install scarletkc/agents <skill> --agent codex --scope user. In an environment that supports npx, the alternative interactive global command is npx skills add scarletkc/agents -g; to choose a skill and assistant non-interactively, run npx skills add scarletkc/agents --skill <skill> --agent codex -g -y. Replace codex with another supported assistant, such as claude-code, when appropriate.

How do you use this agent?

Review the available skills and select only the workflows you need; each skill's full activation description and instructions live in its own skills/<skill>/SKILL.md. For repository-level guidance, copy the root AGENTS.md into the target repository and prepend that project's structure, commands, and domain notes. Keep personal collaboration preferences separate using user/AGENTS.md. Once installed, give the chosen coding assistant a task matching the skill's activation description so it can read and apply the relevant SKILL.md. Update all GitHub CLI-installed skills with gh skill update --all, or update global skills CLI installations with npx skills update -g -y. To create an uploadable archive, run python scripts/package_skill.py <skill> and use the resulting dist/<skill>.zip.

What are this agent's strengths and limitations?

Pros
  • It separates project guidance, user collaboration preferences, and task-specific skills into distinct reusable scopes.
  • It explicitly targets Codex CLI and Claude Code while using file formats that other readers of AGENTS.md or SKILL.md can consume.
  • The catalog covers planning, scope control, writing, promotional content, worktree PR preparation, and multiple CLI delegation workflows rather than one generic prompt.
  • It provides two documented installation paths with individual skill selection, plus a script for producing standalone ZIP packages.
  • CLI skills bundle their shared task runtime, and the repository includes a synchronization step whose consistency is checked by the test suite.
Limitations
  • It is not an autonomous agent or hosted service; execution depends on an external coding assistant or CLI that reads the files.
  • The source does not provide a skill-by-skill compatibility matrix, so behavior outside Codex CLI and Claude Code requires verification.
  • Installation depends on GitHub CLI or an npx-capable skills CLI and requires network and local filesystem access.
  • Packaging and runtime synchronization use Python scripts, but no required Python version or complete environment specification is given.
  • The README exposes only skill summaries, so adopters must inspect each SKILL.md before accepting its triggers and detailed instructions.

How does this agent compare with similar options?

product-writing is presented as the compact option for product copy and technical documentation, leaving more structural and editorial decisions to the task. ux-writing retains a more detailed rule set for clarity, consistency, durable facts, and removal of intermediate state. The repository recommends choosing one of the two guides for a task.

Key facts side by side with the most closely related agents.

Agent Source review Form / cost Stars Updated Language Full support on
Agents Standards & Skills This agent 73 · Some gaps Agent plugin / skillFree ★ 227 6d ago Python Codex · Claude Code
Code Abyss: Persona and Engineering Skills for Coding Agents 60 · Some gaps CLI ★ 245 3mo ago JavaScript Codex · Claude Code
oh-my-agent 60 · Some gaps CLIFree + model costs ★ 1.4k today TypeScript Codex · Claude Code
Spec Kit Skills for Coding Runtimes 53 · Major gaps Agent plugin / skill ★ 172 6d ago Shell Codex · Claude Code

How does FollowAgents rate this agent?

FollowAgents source review · FARS-2.1
Some gaps
73/ 100 5-point scale 3.7 / 5
Trust 18/29
Reliability 11/14
Adaptability 16/18
Convention 13/18
Effectiveness 10/13
Verifiability 5/8
Why each dimension lost points
Trust18 / 29 · 3.1/5

AGENTS.md instructs contributors not to commit credentials, to sanitize paths and untrusted input, and to keep secrets in dedicated configuration channels. The Devin skill limits permission responses to one use and defaults to denying several high-impact operations; the Antigravity skill also rejects bypassing approval to avoid a denial. README installation and update commands help users understand the external steps. Deductions: these are guidance rather than enforced controls, and the supplied material does not fully document data flows, sensitive-data handling, or dependency review across all skills.

Reliability11 / 14 · 3.9/5

AGENTS.md calls for visible errors, no silent degradation, and failure coverage. Several offline agent fixtures model authentication failures, timeouts, permission denials, malformed output, and nonzero exits; CI lists test and validation steps. These sources support one another. Deductions: fixtures do not establish actual run results, and the supplied skill files are truncated or sampled, so repository-wide consistency cannot be checked.

Adaptability16 / 18 · 4.4/5

The skills cover planning interviews, writing, UX, scope control, worktrees, and several external coding agents. README identifies Claude Code, Codex CLI, and other agents that read the relevant formats as audiences. Skill descriptions generally specify triggers and exclusions, and give environment prerequisites such as Python versions and existing installation or authentication. Deduction: compatibility details across agent environments are incomplete in this sample.

Convention13 / 18 · 3.6/5

README organizes the base guidelines, user preferences, and skills; it includes a skill index, installation, updating, packaging, contribution, and feedback guidance. The repository provides an Apache-2.0 license and README points to NOTICE. Deductions: the sample shows no version policy or changelog, cannot establish naming stability across the full repository, and provides CLI installation guidance without showing installation details for every agent.

Effectiveness10 / 13 · 3.8/5

Each skill gives task-specific guidance. README provides actionable install, update, and packaging commands, while CLI skills describe starting, following up, and checking results, making the expected outputs reasonably usable. Reusable skills can reduce repeated setup, but the material does not compare or quantify their value or cost savings, so full marks are not warranted.

Verifiability5 / 8 · 3.1/5

The README skill catalog points to individual SKILL.md files, making instructions traceable. The CI workflow names tests, catalog validation, and a skill-publishing dry run; offline fixtures provide evidence for several failure scenarios. Deductions: these files do not prove CI passed, the sources corroborate only some workflows, and the supplied sample is incomplete.

Risks and how to mitigate them
  • This is a low-confidence static review of a sample; tests were not run and unprovided files were not checked.
  • Some skills invoke external CLIs, access workspaces, and may request tool permissions; users should check permissions, working directories, and outputs as directed by each skill.
Evidence confidence: Low Reviewed Nov 08, 2026 Reviewed revision 8e149b335e96
See the full review method →
Maintain this project? Add the FARS badge to your README

The badge shows the current review score and verdict and links back to this page. It refreshes about once an hour after a re-review.

FARS

[![FARS review](https://followagents.com/badge/scarletkc-agents.svg)](https://followagents.com/en/agents/scarletkc-agents)
<a href="https://followagents.com/en/agents/scarletkc-agents"><img src="https://followagents.com/badge/scarletkc-agents.svg" alt="FARS review"></a>

FAQ

Does this repository execute code or call a model API by itself?
No. It is documented as a standards and skills repository; Codex CLI, Claude Code, or another compatible assistant provides the execution environment.
Does installation require an API key or paid service?
No required API key or fee is documented. Individual delegation skills may rely on external CLI products, but their account, authentication, and pricing requirements are not specified in the supplied material.
Can I install only one skill?
Yes. The GitHub CLI command accepts <skill> after the repository name, and the skills CLI supports --skill <skill>.
How are project rules kept separate from personal preferences?
Repository-level guidance belongs in the target project's AGENTS.md, while user collaboration preferences are maintained separately in user/AGENTS.md.
What troubleshooting guidance is available if installation fails?
No dedicated troubleshooting procedure is documented. You can verify shell access, networking, the GitHub CLI or npx environment, and destination write permissions; other problems can be reported through the repository's GitHub Issues.
Was this page helpful?
View on GitHub ↗ Install ↓

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.