From packport
Create or extend portable pack source using packport conventions. Use when a user wants a new pack, asset, skill, command, agent, instruction, or packaging contract.
How this skill is triggered — by the user, by Claude, or both
Slash command
/packport:author-packThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to author readable portable source under `packs/` while keeping generated target output and local configuration out of pack source.
Use this skill to author readable portable source under packs/ while keeping generated target output and local configuration out of pack source.
PACK.md, skills/<name>/SKILL.md, commands/<name>/COMMAND.md, agents/<name>/AGENT.md, instructions/<name>/INSTRUCTION.md, or hooks/<name>/HOOK.md.PACK.md with only name, version, and description frontmatter when the pack is new.ASSET.md only for non-obvious payload paths, declared portable refs, dependencies, needs, configuration, or source constraints.config, tool, or mcp portable refs and declare each concrete ref in PACK.md or ASSET.md.packport check <root>. If working from the packport source tree before a binary is installed, run bun src/cli.ts check <root>..packs/, native marketplace files, or pack.lock.yaml by hand.ASSET.md when directory conventions are enough.npx claudepluginhub dhruvbaldawa/packport --plugin packportCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.