Skill conceptualization

Exploring how knowledge and experience become reusable skills. Personal judgment guides their use; practice can reshape them.

Public statusPublic in worldview

Self-hosting statusDocumentation first

Runtime boundaryPublic definitions exclude device settings, credentials and current runtime state

SOURCE / GITHUB

The current public README on the main branch. Earlier architecture and stage descriptions are retained there as part of the concept’s history; this site states the current scope.

Read the skill definition on GitHub

From knowledge to ability

An early sketch began with distilling knowledge: knowledge supports skills, and personality puts those skills to use. Exploration can start by asking what to understand, how to judge, what to do and how to check results.

More than an installation format

A capability card describes the ability. Platform instructions, scripts and tools give it usable forms; runtime records describe a particular setting. These parts can evolve separately, with links through their sources and the checks used to assess results. Knowledge, judgment, action and checks can become modules where independent reuse is useful.

Practice writes back

A first card is not proof that an ability is mature. When the knowledge or checks are still unclear, exploration comes first. Repeated use and failure can change the method, its boundaries and the grammar used to make the next skill.