Skillport distribution system

Skill ArthurZakirov/SkillPort/skills/skillport-distribution-system

Package agent skills once. Install them anywhere.

Install

npx -y skills add ArthurZakirov/SkillPort --skill skillport-distribution-system

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when packaging, publishing, or updating a public agent-skill repository so it can be installed across machines, repos, Codex, Claude Code, and local skill directories.

SKILL.md

1.9 KB, 392 tokens by cl100k_base, as published. Nobody here has run it

SkillPort Distribution System

Purpose

Package reusable agent skills once so they can be installed and shared across machines, people, repos, Codex, Claude Code, and local skill directories.

Use This Workflow

For a new skill-pack repo:

Pick the repo product name, slug, and promise before packaging files.
Run scripts/create-agent-skill-repo.sh from the SkillPort repo when starting a new skill pack.
Inspect generated placeholders, plugin manifests, README, examples, schemas, and setup script.
Add or update the real skills.
Add the GitHub repo shorthand to a SkillPort manifest, usually config/skill-repos.local.yaml.
Validate locally with:

npx skills add /path/to/generated/repo --list

Push to GitHub.
Validate from GitHub:

npx skills add https://github.com/OWNER/REPO --list

For normal cross-machine syncing, use:

./scripts/skillport-sync.sh

This reruns npx skills add <repo> --skill '*' -a codex -g -y for every repo listed in the selected manifest, then runs npx skills update -g -y.

Keep personal repo lists in ignored local files such as config/skill-repos.local.yaml, or pass a separate manifest with --repos-file. The public SkillPort repo should only ship a neutral example manifest.

Use the sync script for normal machine setup. Use local symlink scripts only for active local development where live edits should be visible before pushing.

GitHub Template Rule

GitHub template repositories copy an entire repo. They do not directly template a subdirectory.

Use the generator for normal SkillPort workflows. Create a separate minimal GitHub template repo only if you need the GitHub UI or gh repo create --template flow.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.