1min.

1MIN · AI & AGENTS

Portable agent skills still need host-specific access and checks

GitHub’s practical guide separates reusable agent instructions from project configuration and runtime permissions. In its data-pipeline example, related skills read a shared manifest and use one platform adapter instead of inventing separate connection paths. Instructions describe human checkpoints, while repository rules and CI enforce blocking checks. Sharing a skill does not grant credentials or make its tools available in another client.

GitHub Blog · Nov 12, 2026

Why it matters

Teams can reuse engineering procedures without confusing portable text with a complete, enforceable application.

More context

Try documenting one bounded task, keeping project names and schemas in a separate manifest. After packaging for another client, check skill discovery, references, tool access and expected evidence. The guide’s independent-review example performs static diff review rather than running tests.

Keep in mind

An implementation guide with examples, not proof that every skill is portable unchanged. Long-running control, shared state and externally enforced permissions may require an application rather than model instructions.

Original read

More engineering ideas, one minute at a time.

Explore more stories