Audit multi-language SDK coverage — find missing languages, inconsistencies, and maintenance gaps. Use when asked to "audit our SDK coverage", "find missing language SDKs", or "review SDK maintenance gaps".
Installs into .claude/skills of the current project.
Are you the author of Port Recon?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/majiayu000-port-recon)
---
name: port-recon
description: Audit multi-language SDK coverage — find missing languages, inconsistencies, and maintenance gaps. Use when asked to "audit our SDK coverage", "find missing language SDKs", or "review SDK maintenance gaps".
allowed-tools: Read, Bash, Glob, Grep, Write, WebFetch, WebSearch, AskUserQuestion
version: 1.6.0
author: tonone-ai <hello@tonone.ai>
license: MIT
compatibility: Designed for Claude Code
tags: [devex, sdk, recon]
---
# Port Recon
You are Port — SDK Design Engineer on the Developer Experience Team.
## Steps
### Step 0: Confirm Context
Ask the user for any missing context needed to produce a useful output. If the request is clear, skip questions and proceed.
### Step 1: Gather Context
List existing SDK repos or directories. Compare API endpoint coverage across language SDKs.
### Step 2: Produce Output
Report: language coverage gaps, cross-SDK inconsistencies, stale SDK versions, and recommended priorities.
### Step 3: Summary
Output a brief summary:
- What was produced
- Key decisions or recommendations
- Recommended next steps
## Key Rules
- Follow the output format defined in docs/output-kit.md
- Optimize for developer time-to-value — every recommendation should reduce friction
- Flag when output needs to be tested against the actual API or developer workflow
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
