Files
phronesis/README.md
T
nvaldez 64373b7b1a fix v0.1.1: README links absolute - relative paths broke on the PyPI page
PyPI resolves the packaged README's relative links against the project
URL (https://pypi.org/project/phronesis/0.1.0/skill/... -> 404), so all
./skill/, CONTRIBUTING.md, and LICENSE links now point at the gitea web
UI (src/branch/master). Version bumped 0.1.0 -> 0.1.1 - a published
version's description is immutable.

Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
2026-11-19 11:00:55 +01:00

4.5 KiB

phronesis

A chest of skills: a repository of SKILL.md instruction packages and a CLI that lists them and installs them into an agent harness such as Vibe.

The name is phronesis — Aristotle's word for practical wisdom: the knowledge a skilled practitioner has, as opposed to abstract theory (episteme).

Install

pipx install phronesis       # or: pip install phronesis
phronesis                    # list every bundled skill

Command line

phronesis                                    list every skill
phronesis <category>                         filter the list
phronesis <skill>                            show one skill and an install hint
phronesis <skill> --install [--harness <name>]   install globally (~/.vibe/skills)
phronesis <skill> --project [--harness <name>]   install in the project only (.vibe/skills)
phronesis --update                           update every installed skill
  • Already-installed skills prompt before being overwritten; -f / --force skips the prompt.
  • Installations are recorded in a per-machine state file (~/.config/phronesis/installed.json), which powers --update.
  • Shell completion via argcomplete; run activate-global-python-argcomplete once after pipx install.

The example table:

Phronesis Version: 0.1.0

skill        version  category
-----------  -------  ----------
python-tdd   1.2.0    development
        Minimalist TDD architect for Python work

Layout

phronesis/
├── src/phronesis/          # the CLI package (cli, registry, harnesses, state, ...)
├── test/                   # pytest suite
├── skill/                  # one directory per skill; ships as package data
│   └── python-tdd/SKILL.md
├── autotest.py             # every repo check, single entry point
├── SPEC.md                 # the full specification (sectionized, citable)
├── README.md, CONTRIBUTING.md, LICENSE
└── pyproject.toml, requirements.txt

Skills

Skill Version Category Purpose
fiona 2.2.0 productivity Operate an llm-wiki with the fiona-assistant CLI
memory 1.0.1 productivity Give a skill its own MEMORIES.md beside its SKILL.md
python-tdd 1.2.0 development Minimalist TDD architect for Python work
sectionize-markdown 1.2.0 documentation Number headings and list items so each rule can be cited
specification-writer 1.1.0 documentation Write structured, maintainable SPEC.md files

Checks

autotest.py verifies every script and markdown file in the repo:

  • sanity — LF line endings, no committed private keys, file size limit
  • python_syntax — every .py file parses (ast.parse)
  • pycodestyle — PEP 8 style on every .py file
  • shellcheck — every shell script (.sh, .bash, or shebang)
  • frontmatter — every skill/<name>/SKILL.md carries a --- fenced YAML header with name, version, description, category; name matches the directory, version is x.y.z, category is kebab
  • markdown — markdownlint on every .md file, via pymarkdownlnt with front-matter support; md013 (line length) and md033 (inline HTML) are ignored, and md025 treats front-matter title keys as headings off, so skills with a title plus one # stay clean
  • pytest — the suite in test/ with 75 percent coverage floor

Run all checks:

python -m pip install -r requirements.txt
python -m pip install -e .
python autotest.py               # every check
python autotest.py frontmatter   # only the named checks

Adding a skill

See CONTRIBUTING.md. The short version: one directory per skill under skill/, everything the agent needs in a single SKILL.md, and python autotest.py green before you commit.

License

MIT