agentreadme

Report · marked 26 Aug 2026

sickn33/agentic-awesome-skills

Ready for an agent to work in without hand-holding.

Python · 45,384 stars · 20,996 files · branch main

Fix these first

01
Environment config
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
02
Lint and format rules
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
03
Static type checking
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

The full marking

Every deduction below names the file or setting it came from.

Instructions 25/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

Agent instruction file 12/12
AGENTS.md is present, which is the format the most tools read.
Instruction quality 10/12
Specific enough that an agent can act on it.
Worth fixing: has no code blocks.
6,765 characters, a workable length
names the actual commands to run
uses headings, so an agent can skim it
README as an entry point 3/3
README has a clear getting-started section.
Setup 14/18 A-

Whether an agent can install the project and get it running without a human.

Deterministic install 6/6
package-lock.json pins the dependency tree.
Found package-lock.json
Discoverable commands 6/6
Commands are declared where an agent will look for them.
package.json scripts (validate, validate:glossary, validate:strict, audit:skills, audit:skills:strict, fix:missing-sections…)
scripts/ directory
Environment config 0/4
Nothing documents the environment this needs. An agent will get a runtime error it can't diagnose.
Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.
Pinned runtime version 2/2
The language runtime version is pinned.
package.json engines.node >=22
Reproducible environment n/a
Not applicable — a library doesn't need a container to be worked on.
Verification loop 17/25 B

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

Tests exist 6/8
261 test files against 3080 source files.
e.g. apps/web-app/scripts/generate-sitemap.test.js, apps/web-app/scripts/verify-seo-assets.test.js, apps/web-app/src/__tests__/App.performance.test.tsx
Test command is discoverable 7/7
An agent can find and run `npm run test`.
Continuous integration 4/4
9 GitHub Actions workflows define what "passing" means.
Lint and format rules 0/3
No linter or formatter config. Style is tribal knowledge, so agent output will drift from yours.
A formatter config is the cheapest way to stop reviewing whitespace in agent diffs. It moves style from opinion to a command.
Static type checking 0/3
No static type checking.
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.
Context economy 19/20 A+

Whether the repo fits in a context window, or fights it.

No committed build output 6/6
No generated directories committed.
.gitignore hygiene 3/3
.gitignore covers 43 patterns.
File sizes fit in context 6/6
No source file is large enough to crowd out a context window.
Repository weight 4/5
About 124.4MB checked out, which is comfortable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for sickn33/agentic-awesome-skills
# AGENTS.md

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,005+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

## Setup

```
npm ci
```

## Commands

```
npm run build                  # produce a build
npm run test                   # run the test suite, must pass before any commit
npm run validate
npm run validate:glossary
npm run validate:strict
npm run audit:skills
npm run audit:skills:strict
npm run fix:missing-sections
```

## Layout

- `plugins/`      1757 source files
- `skills/`       1020 source files
- `tools/`        237 source files
- `apps/`         56 source files
- `verification/` 4 source files
- `scripts/`      3 source files

## Conventions

- Tests live alongside the code they cover, following `apps/web-app/scripts/generate-sitemap.test.js`.
- CI defines what passing means. See `.github/workflows/aas-agent-first-preview.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown  or  curl -o AGENTS.md agentreadme.com/draft/sickn33/agentic-awesome-skills.md

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

agent ready 85 out of 100

[![agent ready](https://agentreadme.com/badge/sickn33/agentic-awesome-skills.svg)](https://agentreadme.com/sickn33/agentic-awesome-skills)

Other Python repositories, marked

vinta/awesome-python 81 A- NousResearch/hermes-agent 84 A- TheAlgorithms/Python 66 B yt-dlp/yt-dlp 54 C+ Significant-Gravitas/AutoGPT 63 B microsoft/markitdown 46 C

All Python repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in