# skills.sgit.ai — brief pack

**For:** the agent commissioned to build `skills.sgit.ai`
**From:** Dinis Cruz, via the SG/Send Librarian
**Version:** v0.33.62 · 24 August 2026
**Licence:** CC BY 4.0 — see `LICENSE.md`

---

## What this is

The skills work, in its two halves:

- **Shipped:** 8 real skills, 16,338 words of SKILL.md, across two repos — plus authoring conventions nobody has written down.
- **Thought:** **25 dedicated briefs, 60,782 words**, the core written in one four-day burst (1–4 June 2026, six briefs on the 4th alone) — the most complete theory of agent skills in the estate.

The site is built around the gap between them, stated honestly.

---

## The thesis

> *"Skills are a software package, that is the best analogy… the same way we have npm and pip for managing dependencies, we need a way to manage skills like that."*

Scored against its own checklist, the estate's skills get **one green cell** (documentation) out of seven lifecycle stages. That table (`03__` §1) is the site's roadmap by another name.

---

## Read in this order

| File | Words | What it does |
|---|---:|---|
| **`00__BRIEF.md`** | 1.3k | **Start here.** The two halves, the thesis, the four original ideas, the shipped/thought gap, the build order |
| **`02__the-shipped-skills.md`** | 0.8k | The catalogue, **the five authoring conventions**, the three governance rules, and **the diverging duplicate** |
| `03__skills-are-packages.md` | 0.8k | The thesis, the one-green-cell lifecycle table, intent-over-capability, the five-step roadmap |
| `05__skills-identity-permissions.md` | 0.6k | A skill comes with its permission set; units of execution; **the OAuth critique**; the one-field frontmatter proposal |
| `01__concepts-index.md` | 0.8k | The 25 briefs mapped into 7 clusters with deconflicts |
| `04__the-skill-economy.md` | 0.7k | Base vaults, the customisation cascade, Tessl, scoring-on-provenance, the dated conference validation |
| `06__site-architecture.md` | 0.4k | Page by page; what must be generated |
| `07__boundaries-and-licensing.md` | 0.4k | Do-not-publish list and network boundaries |
| `08__gaps-and-open-questions.md` | 0.7k | 7 build-fresh items, 6 open questions, 5 tensions |
| `09__source-manifest.csv` | 30 rows | Every source, tiered 0–3, **every path verified on disk** |
| `skills__catalogue.json` | 8 skills | The catalogue as data — the seed for `/catalogue/`, which is the registry v0 |

---

## The three things worth your attention

**1. The diverging duplicate is exhibit A.** `use-sg-playwright` exists in both repos — 1,337 vs 1,379 words, already 42 apart, and the `__Send` copy carries an auth claim the code contradicts. **That is the skills-are-packages thesis failing exactly as predicted, on your own skills.** Lead with it.

**2. The best governance artefact is a decision not to build.** The `sg.llm` skill refusal — *"skills earn their keep when they cover a distinct task"* — generalises into three rules that, with the five authoring conventions extracted from the shipped skills, make a complete `/authoring/` page a visitor can use the same day.

**3. Two questions have no answers and they are the hard version of the thesis.** *What is a skill version*, when the interpreter (the model) changes underneath? And *how do you test intent*? The site should publish both as open questions — they are what "skills are packages" costs when taken seriously.

---

## Deconflicts

The **skill lifecycle** (Explorer→Town Planner, the token-spend line) is owned by `wardley-maps.sgit.ai`. The **OWASP monetisation** thread is owned by `open-source.sgit.ai`. **Meaning through connectivity** is `graphs.sgit.ai`'s. This site states each in three lines and links out — the manifest marks all three.

---

## House pattern

Copy `pki.sgit.ai`, add `/llms-full.txt` — and note the site's particular duty: its subject is the artefact type agents load, so the catalogue must be machine-readable before it is pretty, and everything countable is generated at build time.

---

This file is released under the Creative Commons Attribution 4.0 International licence (CC BY 4.0).