starling-key-inspector

Retrieve Starling localization data by key text with JSON output.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/itsuki0927/opencode --skill starling-key-inspector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starling-key-inspector
Source: https://github.com/itsuki0927/opencode/tree/main/skills/starling-key-inspector
Command: npx skills add https://github.com/itsuki0927/opencode --skill starling-key-inspector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Use this tool to query Starling localization keys by key text and return source text, per-language translation status, and publish status in structured JSON for agent workflows.

Core Features & Use Cases

  • Retrieve source text and per-language translations across projects and namespaces, with status and publish information suitable for automation pipelines.
  • Batch query support across multiple keys with context discovery and JSON output for agent workflows.

Quick Start

Run the tool with a key_text and --json to receive structured results suitable for agent workflows.

Frequently Asked Questions about starling-key-inspector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I query Starling localization keys and retrieve translations for automation pipelines?

Batch query Starling localization keys by passing key text to return source text, per-language translations, and publish status in structured JSON. It handles multiple projects and namespaces, providing context discovery when needed for automation pipelines.

What do I need to retrieve Starling translations across multiple projects and namespaces?

Valid Starling credentials (AK/SK) are required to retrieve translations across multiple projects and namespaces. The tool auto-saves project context and credentials on success, supporting both single and batch queries with structured JSON output.

Can I get structured JSON output from Starling i18n queries for agent workflows?

Yes, use the --json output flag to receive structured JSON from Starling i18n queries. This format returns source text, per-language translation status, and publish information, making it directly consumable by agent workflows.

How does context discovery work when searching for Starling translation keys?

Context discovery automatically identifies relevant project and namespace when searching for Starling translation keys. It handles single or batch queries, ensuring accurate retrieval of source text and per-language translations even when project context is unclear.

What's the best way to batch query multiple Starling keys for per-language publish status?

Batch query multiple Starling keys by providing key text inputs to retrieve source text and per-language publish status in structured JSON. The tool applies across multiple projects and namespaces, auto-saving context for subsequent automation tasks.

Why does my Starling key query require AK/SK credentials to return translations?

Starling key queries require valid AK/SK credentials to authenticate access to localization data across projects and namespaces. Without valid credentials, the tool cannot retrieve source text, per-language translations, or publish status from the Starling platform.