pleaseai/Port Internal Developer Portal
plugins/port/skills/port/SKILL.md
Query and operate Port.io — the Internal Developer Portal that governs your SDLC. Use when working with software catalogs, blueprints, entities, scorecards, self-service actions, incidents, or DevOps/platform requests. Triggers on mentions of Port, port.io, IDP, developer portal, scorecards, blueprints, service catalog, or self-service actions.
$ install --global
skillsauthnpx skillsauth add pleaseai/claude-code-plugins Port Internal Developer PortalInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 18, 2026, 6:02 AM364.3s1 file scanned
SKILL.md
- name:
- Port Internal Developer Portal
- description:
- Query and operate Port.io — the Internal Developer Portal that governs your SDLC. Use when working with software catalogs, blueprints, entities, scorecards, self-service actions, incidents, or DevOps/platform requests. Triggers on mentions of Port, port.io, IDP, developer portal, scorecards, blueprints, service catalog, or self-service actions.
- allowed-tools:
- mcp__port-us__list_blueprints, mcp__port-us__list_entities, mcp__port-us__list_actions, mcp__port-us__list_scorecards, mcp__port-us__run_action, mcp__port-us__track_action_run, mcp__port-us__describe_user_details, mcp__port-us__search_port_knowledge_sources, mcp__port-us__get_sidebar, mcp__port-us__load_skill, mcp__port-eu__list_blueprints, mcp__port-eu__list_entities, mcp__port-eu__list_actions, mcp__port-eu__list_scorecards, mcp__port-eu__run_action, mcp__port-eu__track_action_run, mcp__port-eu__describe_user_details, mcp__port-eu__search_port_knowledge_sources, mcp__port-eu__get_sidebar, mcp__port-eu__load_skill
Port Internal Developer Portal
Use the Port MCP tools automatically when the user works with their Internal Developer Portal — the software catalog, scorecards, self-service actions, or any SDLC governance task on Port.io.
Regions
Port operates in two regions, exposed as two MCP servers in this plugin:
| Region | MCP server | Endpoint |
|--------|------------|----------|
| US | port-us | https://mcp.us.port.io/v1 |
| EU | port-eu | https://mcp.port.io/v1 |
Use one region — whichever matches the user's Port account. If unsure which region they are on, call describe_user_details on each and use the one that authenticates, or ask. Do not duplicate calls across both regions.
When to Use
- Catalog discovery: list blueprints/entities, find services, owners, dependencies.
- Scorecards & quality: check scorecard rules, levels, and which entities pass/fail.
- Self-service: list and run self-service actions, then track their run status.
- Knowledge: answer questions about the org's software using
search_port_knowledge_sources. - Portal config: inspect the sidebar, manage folders and dashboard widgets.
How to Use
- Start with
describe_user_detailsto confirm the active org/region when context is missing. - Use
list_blueprints→list_entitiesto explore the catalog before answering catalog questions. - Use
list_scorecardsfor quality/compliance questions. - For self-service:
list_actionsto find the action,run_actionto execute, thentrack_action_runto monitor until completion. Confirm with the user before running any action that creates or changes infrastructure. - For org-knowledge questions, prefer
search_port_knowledge_sourcesover guessing.
Important Notes
- Authentication is handled by the Port MCP server's OAuth flow (
/mcpto connect). No API key env var is required. run_actionmay trigger real infrastructure changes — treat it as a write operation and confirm intent first.- Some MCP servers expose additional capabilities via
load_skill; call it to discover Port-specific guided workflows when available.
Related Skills
pleaseai/plugins/workflow-sdk/agent/skills/workflow
tools
VerifiedTrustedCommunity
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
11SKILL.mdUpdated Jul 8, 2026
pleaseai/plugins/workflow-sdk/agent/skills/workflow-init
tools
VerifiedTrustedCommunity
Install and configure Vercel Workflow SDK before it exists in node_modules. Use when the user asks to "install workflow", "set up workflow", "add durable workflows", "configure workflow sdk", or "init workflow" for Next.js, Express, Hono, Fastify, NestJS, Nitro, Nuxt, Astro, SvelteKit, or Vite.
11SKILL.mdUpdated Jul 8, 2026
pleaseai/plugins/workflow-sdk/agent/skills/migrating-to-workflow-sdk
tools
VerifiedTrustedCommunity
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.
11SKILL.mdUpdated Jul 8, 2026
pleaseai/plugins/wordpress/agent/skills/wpds
tools
VerifiedTrustedCommunity
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
11SKILL.mdUpdated Jul 8, 2026