evaluate-new-port Skill
Audit a vcpkg port locally. Reads the port metadata and build recipe, installs the port, inspects extracted sources and installed files, and produces a report covering license risks, vendored code, optional dependencies, and other port review suggestions. Published by microsoft in vcpkg.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
1 month ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is evaluate-new-port Skill?
Audit a vcpkg port locally. Reads the port metadata and build recipe, installs the port, inspects extracted sources and installed files, and produces a report covering license risks, vendored code, optional dependencies, and other port review suggestions. Published by microsoft in vcpkg. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: .github/skills/evaluate-new-port/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use evaluate-new-port Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/vcpkg
- Skill file: .github/skills/evaluate-new-port/SKILL.md
What it does
Audit a vcpkg port locally. Reads the port metadata and build recipe, installs the port, inspects extracted sources and installed files, and produces a report covering license risks, vendored code, optional dependencies, and other port review suggestions.
Skill instructions
Evaluate New Port When to Use - Reviewing a newly added or substantially updated port - Auditing whether a port's declared license metadata matches what it installs - Checking for vendored third-party code or optional dependencies that are not modeled in vcpkg.json - Looking for packaging or review issues after a real local install Overview This skill takes a single port name, reads the port's metadata and build recipe, performs a clean local install, and writes a structured audit report. The audit focuses on: - Declared license metadata from ports/{port-name}/vcpkg.json, including feature-scoped declarations - Build invocation and feature toggles from ports/{port-name}/portfile.cmake - Real build output after vcpkg x-ci-clean and vcpkg install {port-name} - Extracted source tree under buildtrees/{port-name}/src - Installed package contents under packages/{port-name}{target-triplet} - Code review suggestions for the port's packaging logic and metadata If the install reports that the po
Verified compatibility and discovery
Frequently asked questions
What is evaluate-new-port?
evaluate-new-port is a open-source AI agent skill with Copy skill directory. Audit a vcpkg port locally. Reads the port metadata and build recipe, installs the port, inspects extracted sources and installed files, and produces a report covering license risks, vendored code.
Who is evaluate-new-port best for?
evaluate-new-port is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install evaluate-new-port?
Install or run evaluate-new-port using Copy skill directory. Check evaluate-new-port for the latest setup command.
Is evaluate-new-port actively maintained?
evaluate-new-port may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
