Slide contents

1. 1. Agent Skills: Procedures, Knowledge and Trust

   With Maxim Smirnov: from a working skill to Open Knowledge Format

2. 2. A skill has four jobs

   Package a procedure, select it, check its output, maintain its knowledge

3. 3. A loop needs a repeatable procedure

   A trigger starts work; a skill describes it; a verifier accepts the result

4. 4. Each layer has a different responsibility

   Project guidance, task methods, connections, events and knowledge

5. 5. A skill starts with a folder

   SKILL.md states the purpose; neighboring files supply detail and helpers

6. 6. Context loads when it is needed

   Skill catalog → selected instructions → relevant resource

7. 7. Skill selection can fail too

   Test missed activation as well as unnecessary activation

8. 8. Portability has boundaries

   Compatible files do not guarantee identical permissions or behavior

9. 9. Test selection and output separately

   Loading instructions is an intermediate event, not the success criterion

10. 10. Services have grown around the format

    Installation, discovery, package scanning and programmatic access

11. 11. Procedures need current knowledge

    The diagnostic method may persist while ownership and policies change

12. 12. OKF links files into a graph

    Open Knowledge Format (OKF): knowledge in linked Markdown files

13. 13. One medium, different contracts

    Agent Skills describes a package; OKF describes a knowledge document

14. 14. Knowledge has a verification history

    Source, modification, verification and expiry are different events

15. 15. Check the definition and the run

    Approved computation → parameters → execution → receipt → check

16. 16. The receipt also needs trust

    Checking supplied data does not authenticate a remote execution

17. 17. A skill can guide knowledge access

    Skill discovery → section map → relevant document

18. 18. A format does not choose retrieval

    Navigation, search and hybrid approaches can read the same corpus

19. 19. An example does not establish superiority

    A specification, demo, experiment and deployment answer different questions

20. 20. The harness owns execution

    Versions, permissions and independent checks connect files to outcomes

21. 21. Start with one recurring task

    One skill, known sources and an inspectable output

22. 22. Knowledge becomes useful through verification

    Capture the procedure, identify the source, evaluate the outcome