skills.rest
NeptuneKit
NeptuneKitOFFICIAL
Explore all skills by this author →
GitHub

tritonkit-emulator-cli-takeover

Designs and validates TritonKit CLI takeover of iOS, Android, and HarmonyOS emulators.

1|Updated May 15, 2026
Search Tags:#automation#cli#evidence capture#ios simulator#android emulator#harmonyos#schema contracts
One-click install
npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-emulator-cli-takeover-neptunekit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tritonkit-emulator-cli-takeover
Source: https://github.com/NeptuneKit/TritonKit/tree/main/TritonKit.skills/tritonkit-emulator-cli-takeover
Command: npx skills add https://github.com/NeptuneKit/TritonKit --skill tritonkit-emulator-cli-takeover-neptunekit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It guides engineers through designing, implementing, and validating TritonKit's local CLI control surface for iOS Simulator, Android Emulator, and HarmonyOS / DevEco Emulator, keeping every capability schema-backed, machine-readable, and within the local-only product boundary. ## Core Features & Use Cases - CLI Admission Decisions: Decide whether a capability belongs in the triton CLI, covering target discovery, app lifecycle, observation, actions, evidence, and replay while excluding Web UI, remote agents, real devices, and device clouds. - Schema-Backed Contracts: Keep triton schema, capabilities, doctor, and plan outputs aligned with failure codes, recovery categories, and JSON/JSONL output contracts. - Safety and Evidence Policy: Enforce destructive-action flags, bounded and redacted evidence, ambiguous-target handling, and verification of business postconditions rather than host command success. - Use Case: When adding a new triton device proxy or sim command, use this Skill to route to the right reference file, write failing tests first, update schemas and docs, and validate with focused test runs. ## Quick Start Ask the agent to design and validate a new triton CLI command for iOS Simulator screenshot capture following the emulator takeover workflow.

Frequently Asked Questions about tritonkit-emulator-cli-takeover

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

FAQPage Schema
How do I decide whether a capability belongs in the triton CLI?▼

A capability belongs in the triton CLI when an agent needs it to prepare, observe, execute, verify, replay, or archive a local emulator regression with machine-readable output. Web UI, remote orchestration, real-device flows, and central services are excluded by default.

How do I add a new triton CLI command for iOS Simulator or Android Emulator?▼

Update the space README with BDD acceptance, add failing model/parser tests, implement shared DTOs before CLI glue, register the command in commandSchemas(), then sync docs and skills. Validate with swift test and schema inspection commands.

Does TritonKit support real devices or remote device clouds?▼

No. The emulator takeover surface is local CLI plus local simulator/emulator only. Real-device targets return errors such as proxy_real_device_not_supported, and remote agents, device clouds, and Web control surfaces are explicitly out of scope.

Why does a destructive triton command return destructive_action_requires_policy?▼

Destructive or state-changing host actions require explicit policy flags such as --confirm, --audit-record, and --execute-runner. Without them the command refuses to mutate host or emulator state and returns the policy error envelope.

When should I fall back to simctl, adb, or hdc instead of triton commands?▼

Fall back only after preserving a Triton fact source via status, doctor, capabilities, or schema commands, and only when Triton proves failure, unsupported scope, or missing schema coverage. Record both the Triton error evidence and the fallback command in the report.

Related Skills

Explore More Software Engineering Skills→
glittercowboyglittercowboy
2.0k

build-iphone-apps

Build, test, debug, and ship native iOS apps in Swift using CLI-only workflows.

Community
Advanced
ThalesGroupThalesGroup
19

agilab-testing

Execute targeted AGILAB tests across unit, smoke, and regression suites.

Official
Advanced
AdeitasunaAdeitasuna

bug-triaging

Triages bug reports into structured phases and generates triage and sprint documents.

Community
Advanced
mattleibowmattleibow
1

maui-ai-debugging

Build, deploy, inspect, and debug .NET MAUI and MAUI Blazor Hybrid apps.

Community
Advanced