What problem does it solve? Publishing a Specs Lens involves many error-prone manual steps: fixing project metadata, setting up a production signing key, generating a Lens icon, exporting a signed SnapOS Package, registering the release, uploading media, assigning a content rating, and submitting for review. This Skill orchestrates that entire pipeline from a single request, with one consolidated confirmation before any irreversible action. ## Core Features & Use Cases - End-to-end publish pipeline: Runs Discover, Preflight, Package, Publish, and Submit phases using pinned scripts for signing-key setup, Lens icon generation, SPK export, and authorized API calls. - Single consolidated confirmation: Proposes missing Lens name, description, tags, category, content rating, icon, and signing-key plan, then asks for one approval before mutating the project or submitting. - Local moderation and content rating: Performs an advisory local moderation check and proposes a full Dev Dash content-rating assessment with a computed target age rating. - Use Case: A developer finishes a Lens in Lens Studio and asks the agent to publish it; the Skill validates the project, generates a 320x320 icon if missing, exports the production SPK once, uploads it with preview media, persists the age rating, and submits the release for review. ## Quick Start Ask the agent to publish the Lens project at the path to your .esproj file, for example by saying: publish my Specs Lens at /path/to/MyLens.esproj.
