Translation coordinator
Skill jlreyes/swift-agent-kit/skills/translation-coordinator
Swift development kit for agentic coding: Swift 6/SwiftUI standards, Apple docs lookup with falsification, Xcode-as-MCP-worker operating guide, Apple's Xcode 27 skills via local extraction, and programmatic Instruments analysis
npx -y skills add jlreyes/swift-agent-kit --skill translation-coordinatorAssembled 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.
What its author says it does
Copied from the file, not written here
Orchestrates Xcode String Catalog localization: prepares the project via LocalizationPlanner, fetches untranslated keys by state, and delegates batches to translator subagents that use the translation skill. Use when asked to localize an Xcode project or translate String Catalogs. Requires the xcode-tools MCP server. (Content extracted from your local Xcode on install.)
SKILL.md
1.7 KB, as published. Nobody here has run it
translation-coordinator (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.