[Markdown] Tools for working with agents.
docs Frame the repo as agent assets, not only skills
State that the repo collects every kind of shareable agent configuration — skills, steering, and MCP servers down the road — with one top-level directory per type.
README.org
@@ -1,13 +1,22 @@
1
1
#+TITLE: agent-skills
2
2
#+OPTIONS: toc:nil
3
3
4
Removed:
A collection of reusable Kiro skills, versioned in one place and shared
5
Removed:
across every project.
4
Added:
Reusable Kiro agent assets, versioned in one place and shared across
5
Added:
every project. The repo holds more than skills. It collects every kind
6
Added:
of shareable agent configuration, installed into =~/.kiro= by symlink.
6
7
7
Removed:
* Layout
8
Added:
Content types, present and planned:
8
9
9
Removed:
The repo holds two kinds of shareable content. Skills load on demand as
10
Removed:
slash commands. Steering modules shape every response.
10
Added:
- *Skills* — on-demand slash commands, under =skills/=.
11
Added:
- *Steering* — always-on rules that shape every response, under
12
Added:
=steering/=.
13
Added:
- *MCP servers* — planned. Tool servers the agent connects to, under
14
Added:
=mcp/=.
15
Added:
16
Added:
Each type gets its own top-level directory. Add a new type by adding a
17
Added:
directory and a short section here.
18
Added:
19
Added:
* Layout
11
20
12
21
#+begin_example
13
22
agent-skills/