Audit xcode security settings
Skill jlreyes/swift-agent-kit/skills/audit-xcode-security-settings
Apple's progressive hardening playbook for Xcode build settings: security-oriented compiler warnings, static analyzer checkers, and Enhanced Security features (pointer authentication, typed allocators, hardware memory tagging, read-only platform memory), with a build- settings catalog and a filter script. Use when asked to audit or harden an Xcode project's security posture, enable security warnings or static analysis, or catch more bugs at compile time in C/C++/ObjC/ Swift. Skip for network security, code signing, or privacy APIs. (Content extracted from your local Xcode on install.)From its SKILL.md
npx -y skills add jlreyes/swift-agent-kit --skill audit-xcode-security-settingsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.9 KB, 284 tokens by cl100k_base, as published. Nobody here has run it
audit-xcode-security-settings (stub)
Not yet extracted. This is a stub. The real skill is Apple-authored content that ships inside Xcode; Apple's license doesn't permit redistributing it, so this kit extracts it from YOUR Xcode instead.
To install the real content (requires Xcode 27+, ~5 seconds), run the extraction script that ships alongside these skills. Relative to this skill's own directory it is at:
../apple-api-updates/scripts/extract-apple-skills.sh(In the Claude Code plugin layout it is also exposed at the plugin root as scripts/extract-apple-skills.sh. If apple-api-updates is not installed alongside, install it — the script ships inside it.)
If you are an agent reading this: resolve this SKILL.md's path and run that script with your shell tool. Skill bodies are cached for the session and you cannot run /reload-plugins yourself (it's a user command), so after extracting: answer the current request by reading the extracted SKILL.md and its references/ directly from disk (plain markdown, fully usable), and ask the user to run /reload-plugins — or start a new session — so future invocations serve the real content.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.