Skip to main content
A skill that describes how to work on a codebase belongs with that codebase. Instead of copying it into Devic and watching the two drift apart, connect a folder skill to a folder in a GitHub repository: the repository stays the source of truth, and Devic reads from it.
This applies to folder skills only. The connected folder must contain a SKILL.md at its root — that file is what makes it a skill.

Connecting one

1

Connect your GitHub account

Once per user, from the account settings. Devic uses your token, which is also why you can connect a public repository that belongs to somebody else.
2

Pick the folder

Create a skill and choose from GitHub. You browse the repository’s tree rather than typing a path; folders holding a SKILL.md are marked and selectable, so the selection is valid by construction. A repository can hold many skills — one folder each — which is how public skill collections are laid out.
3

Choose the branch

The skill follows a branch. Change it later from the skill’s card and the content follows.
The skill then behaves like any other: it appears in the catalogue, it is attached to agents and assistants the same way, and it is injected into the prompt the same way. A skill connected to GitHub

What “live” means

Nothing is copied into Devic. When the agent loads the skill, Devic fetches the files from the repository and serves them, cached for five minutes. The agent walks the folder exactly as it walks any other skill: it reads SKILL.md first, then opens whatever that file points at. grep_knowledge works too, though on a connected skill it falls back to a lexical search over the repository files rather than a semantic one, since these files have no embeddings in Devic.

Bringing it in

Two operations sit on the skill’s card, under Advanced options:
Import is a fork, not a sync. Once imported, changes on the branch stop reaching Devic and edits in Devic never reach the repository. Import when you want to take a public skill and adapt it; stay connected when the repository is the version that must run.

Skills

What a skill is, and how it reaches the model.

Organising knowledge

Folders, hierarchy and the document graph.