port-skill-creator

Skill creator

A skill here is a plain file in this git repo, read by a third party's coding agent, that helps it get a Port job done: build a context lake, write a mapping, manage Port with Terraform. It is not Port's internal in-product AI skill system (packages/ai-skills in port-labs/port, which creates a skill entity via upsert_entity for Port AI's own runtime). See references/skill-writing-guide.md#adapting-an-internal-skill if you're starting from one of those.

This skill itself lives at .claude/skills/port-skill-creator/, not under skills/, because it's for someone contributing to this repo, not for someone who installed skills/ into their own coding agent to work with their Port account. It never ships to end users; it's only relevant when working in this repo, so it stays repo-local.

Prerequisites

None. This is a reference skill, no live Port account or MCP server needed, just this repo and Node.js to run the scripts below.

File layout

skills/port-<name>/
├── SKILL.md            # required: short frontmatter + router body
├── references/         # one file per sub-topic, the actual depth
└── assets/              # images, scripts, and complete ready-to-run examples

<name> must be lowercase, hyphenated, prefixed with port-, and match the frontmatter name exactly (enforced by validate-skill.js).

How to build a skill

1. Scope it. One sentence on what job this helps do, what it assumes already exists, and what's explicitly out of scope (point to the skill that owns that instead). Check the README so scopes don't overlap. See references/skill-writing-guide.md#scope-it-first.
2. Choose reference vs. MCP-powered. See references/skill-writing-guide.md#choose-a-skill-class.
3. Write the frontmatter, description last. description is the only place "when to use this" lives, packed with realistic trigger phrases. Never restate it as a body section. See references/skill-writing-guide.md#description-the-trigger-signal.
4. Write the body as a router, not a manual. Assume the agent already decided to do the job. State prerequisites, then a short numbered list of what to do, each step pointing at the references/*.md file that has the actual depth. Target well under 100 lines. See references/skill-writing-guide.md#body-is-a-router for the shape and a worked example. Prerequisites should point to the port-getting-started skill for account setup and MCP connection instead of restating it, and should say explicitly that this skill can use Port's MCP server to apply the work directly when connected, and that search_port_knowledge_sources covers anything the skill itself doesn't. See references/skill-writing-guide.md#prerequisites-port-getting-started-and-mcp.
5. Push real content into references/ and assets/. One reference file per sub-topic (references/blueprints.md, references/mirror-properties.md, not one giant references/details.md). Assets are anything ready to use as-is: images, scripts, complete examples.
6. Validate: node .claude/skills/port-skill-creator/scripts/validate-skill.js skills/port-<name> (or --all).
7. Regenerate the README index: node .claude/skills/port-skill-creator/scripts/generate-skill-index.js.
8. Test it for real. Install it (cp -r skills/port-<name> ~/.claude/skills/), run 2-3 realistic trigger prompts in a fresh session, confirm it loads and produces correct, ready-to-apply Port config.