Ry init

Skill NDDev-it-com/rldyour-antigravity-cli/.gemini/skills/ry-init

rldyour Antigravity CLI configuration: native extensions, GEMINI.md context, commands, skills, subagents, hooks, MCP, browser-provider routing, Serena memory, and runtime validation.

Install

npx -y skills add NDDev-it-com/rldyour-antigravity-cli --skill ry-init

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 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

Инициализируй Antigravity CLI adapter scope без изменений. EN: initialize Antigravity CLI adapter scope read-only.

SKILL.md

1.6 KB, as published. Nobody here has run it

Purpose

Build a verified context pack for Antigravity CLI adapter work before implementation.

Native Antigravity Boundary

Use Antigravity GEMINI.md, project settings, TOML commands, Agent Skills, subagents, hooks, policies, and MCP server config. This skill is not a Claude slash command, Codex managed agent, OpenCode command, or cmux orchestrator.

When To Use

Use when the user asks to initialize, inspect, onboard, or prepare for work.

Inputs

User scope and constraints.
GEMINI.md, AGENTS.md, and config/rldyour-contract.json.
Current git/submodule state.
Relevant Serena memories and validator entry points.

Procedure

Read source-of-truth files and relevant memories first.
Map Antigravity native surfaces, runtime baselines, MCP inventory, browser routing, cmux boundary, and quality gates.
Identify unknowns and mark unsupported claims NOT_PROVEN.
Do not mutate files, git state, or system configs.
Return a compact context pack with exact paths and safe next steps.

Evidence Required

Git state, source paths, memory names, validator names, and current tuple facts.

Forbidden Actions

No edits, commits, pushes, branch deletion, system install, or background/headless orchestration.

Acceptance Checks

Context report names exact source-of-truth files and unresolved gaps.

Failure Reporting

Report missing context, blocked evidence, and the next read-only command.