Files
hermes-pi 0226e33ac7 phronesis v0.4.0-dev: add skill linux-server-hardening (security)
- port of the wiki-local linux-server-hardening checklist (v1.2.0) into
  the bundle: audit listeners and accounts, SSH key-only, close unused
  accounts, scoped firewall, fail2ban, unattended-upgrades, surface
  reduction, verify-and-record; new `security` category, announced live
  by the listing per CONTRIBUTING
- SKILL.md body ported verbatim from the source copy; front matter
  adapted to the four-key bundle contract (SPEC 4.2-4.3)
- MEMORIES.md starting template shipped beside it (SPEC 4.7); the
  installed memory is add-only so live instances keep their entries
  (SPEC 6.8)
- tests: bundled load, category listing, and category filter for the
  new skill; autotest fully green (84 tests, 93 percent coverage);
  e2e-verified via the installed pipx CLI

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

108 lines
4.8 KiB
Markdown

# 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](https://mistral.ai).
The name is [phronesis](https://en.wikipedia.org/wiki/Phronesis) —
Aristotle's word for *practical wisdom*: the knowledge a skilled
practitioner has, as opposed to abstract theory (`episteme`).
## Install
```bash
pipx install phronesis # or: pip install phronesis
phronesis # list every bundled skill
```
## Command line
```text
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 <skill> --uninstall remove it again (project scope: add --project)
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:
```text
Phronesis Version: 0.1.0
skill version category
----------- ------- ----------
python-tdd 1.2.0 development
Minimalist TDD architect for Python work
```
## Layout
```text
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](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/fiona/SKILL.md) | 2.2.0 | productivity | Operate an llm-wiki with the fiona-assistant CLI |
| [linux-server-hardening](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/linux-server-hardening/SKILL.md) | 1.2.0 | security | Numbered checklist to audit, harden, and verify an exposed Debian-family Linux server (SSH, accounts, firewall, fail2ban, updates) |
| [memory](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/memory/SKILL.md) | 1.0.1 | productivity | Give a skill its own MEMORIES.md beside its SKILL.md |
| [python-tdd](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/python-tdd/SKILL.md) | 1.2.0 | development | Minimalist TDD architect for Python work |
| [sectionize-markdown](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/sectionize-markdown/SKILL.md) | 1.2.0 | documentation | Number headings and list items so each rule can be cited |
| [specification-writer](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/skill/specification-writer/SKILL.md) | 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:
```bash
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](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/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](https://gitea.nolivaldeziii.com/nvaldez/phronesis/src/branch/master/LICENSE)