Report · marked 10 Oct 2026

sickn33/agentic-awesome-skills

Solid foundations, held back in a few specific places.

Python · 47,410 stars · 26,031 files · branch main

82 /100 A-

Instructions 22/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality and readme as an entry point.Setup 18/20Whether an agent can install the project and get it running without a human. Losing marks on reproducible environment.Verification loop 17/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on tests exist and lint and format rules.Context economy 17/20Whether the repo fits in a context window, or fights it. Losing marks on repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

README as an entry point

Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.

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.

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 22/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.

9,119 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

✗README as an entry point 0/3

No README. This is the first file anything reads, human or machine.

Give the README an Install and a Usage heading with real commands under each. Agents pattern-match on those headings.

Setup 18/20 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 4/4

.env.local.example documents what the app needs to run.

✓Pinned runtime version 2/2

The language runtime version is pinned.

package.json engines.node >=22

✗Reproducible environment 0/2

No container or devcontainer definition.

A Dockerfile or devcontainer removes an entire class of 'it won't install' failures.

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

335 test files against 3262 source files.

e.g. apps/aas-plugin/tests/evidence-fixture.mjs, apps/aas-plugin/tests/local-package.test.mjs, apps/web-app/scripts/docs-metadata.test.js

✓Test command is discoverable 7/7

An agent can find and run `npm run test`.

✓Continuous integration 4/4

10 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 17/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 46 patterns.

✓File sizes fit in context 6/6

No source file is large enough to crowd out a context window.

✗Repository weight 2/5

About 283MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

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,400+ 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/`      1818 source files
- `skills/`       1053 source files
- `tools/`        265 source files
- `apps/`         115 source files
- `verification/` 5 source files
- `scripts/`      3 source files

## Conventions

- Tests live alongside the code they cover, following `apps/aas-plugin/tests/evidence-fixture.mjs`.
- 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

A draft gets the commands right and stops at the things only a maintainer knows. What a good Python AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

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](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 89 A yt-dlp/yt-dlp 54 C+ microsoft/markitdown 48 C+ Significant-Gravitas/AutoGPT 65 B

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