# Community skills

This directory is the landing zone for skills imported from the
[agentskills.io](https://agentskills.io) ecosystem — Goose, Letta, Cursor,
Codex, Copilot, OpenCode, and ~30 other agent products that share the same
SKILL.md format.

## How skills land here

Use `agntspace skill-import <path|git-url|zip-url>` (Phase 5 of
[plan-agentskills-compliance.md](../../../tasks/plan-agentskills-compliance.md))
to bring an external skill into your vault. The importer:

1. Validates the source against the agentskills.io spec.
2. Translates ecosystem form → AgntSpace canonical form (preserving
   `allowed-tools` so a future re-export round-trips losslessly).
3. Lands it in `<vault>/agntspace/system/skills/community/<name>/`.

You can also drop a skill folder directly into `community/` by hand;
SkillLoader auto-discovers it on the next reload.

## Why a separate tier

`community/` is **hash-gated** by SkillSync just like the `core/` tier.
That means:

- A shipped upgrade to a community skill is silently applied when your
  vault copy still matches the previously-accepted hash.
- An upgrade to a community skill that you've edited locally lands in
  the **pending review** queue at `/skills/sync` — your edits are never
  silently overwritten.
- Distinguishing community from `core/` lets the UI flag imported skills
  with their provenance (source URL, import date) so it's always clear
  what came from where.

## How `community/` differs from `private/`

| Tier | Source | Sync behavior |
|---|---|---|
| `private/` | Authored locally; never shipped | Never synced — yours alone, forever |
| `community/` | Imported from the agentskills.io ecosystem | Hash-gated like `core/`; updates surface in the pending queue |
| `core/` | Bundled with AgntSpace defaults | Hash-gated; AgntSpace ships fixes silently when your vault is unedited |
| `_meta/` | Engine substrate (never injected into agent prompts) | Silent overwrite on every boot |

## Authoring a skill that travels well

If you want a skill you write to be portable across products, target
the [agentskills.io specification](https://agentskills.io/specification):

- Required: `name` (lowercase a-z + 0-9 + hyphens, matches parent dir,
  ≤64 chars) and `description` (1-1024 chars).
- Optional: `license`, `compatibility`, `metadata` (extension home),
  `allowed-tools` (space-separated string).
- Validate locally with `agntspace skill-validate <path>`.

AgntSpace adds extra fields like `triggers`, `priority`, `model_tier`,
`tools_granted`, `examples`. Other clients ignore them; they don't break
spec compliance.
