runtime-crew

Coordinate runtime tooling across APEX language parser and sandboxing crates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sahajamoth/apex --skill runtime-crew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: runtime-crew
Source: https://github.com/sahajamoth/apex/tree/main/.agents/skills/runtime-crew
Command: npx skills add https://github.com/sahajamoth/apex --skill runtime-crew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define and enforce clear ownership and workflow for runtime tooling across language parsers, instrumentation, sandboxing, and indexing within APEX.

Core Features & Use Cases

  • Cross-crate ownership: Specifies responsibilities for crates apex-lang, apex-instrument, apex-sandbox, and apex-index.
  • Security-conscious constraints: Ensures sandbox code remains robust and edits stay within owned paths.
  • Validated workflow: Provides a step-by-step process including reviewing changes, writing tests, and running cargo test and clippy.

Quick Start

Follow the workflow to implement a new language target across all affected crates.

Frequently Asked Questions about runtime-crew

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

FAQPage Schema
How do I ensure cross-crate consistency when adding new language parser support?

To ensure cross-crate consistency when adding new language parser support, orchestrate runtime tooling by enforcing ownership constraints across apex-lang, apex-instrument, apex-sandbox, and apex-index. This workflow mandates validation steps including cargo test and clippy.

What is runtime tooling orchestration for language parsers?

Runtime tooling orchestration for language parsers coordinates responsibilities across instrumentation, sandboxing, and indexing components. It defines clear cross-crate ownership and enforces a repeatable, security-conscious workflow to maintain robust sandbox code.

How do I enforce ownership constraints when modifying sandboxing and instrumentation components?

Enforce ownership constraints when modifying sandboxing and instrumentation components by restricting edits to owned paths within the apex-sandbox and apex-instrument crates. This security-conscious approach ensures sandbox code remains robust and validated.

Does the runtime tooling workflow require running cargo test and clippy for language parsers?

Yes, the runtime tooling workflow requires running cargo test and clippy for language parsers. These validation steps are mandatory within the repeatable workflow to ensure code quality and cross-crate consistency before changes are finalized.

What's the best way to coordinate runtime tooling across multiple crates for language targets?

The best way to coordinate runtime tooling across multiple crates for language targets is to apply a defined workflow that specifies responsibilities for apex-lang, apex-instrument, apex-sandbox, and apex-index, ensuring security constraints and required validation are met.

When do I need to orchestrate runtime tooling for language parsers and sandboxing?

You need to orchestrate runtime tooling for language parsers and sandboxing whenever you are adding new language support or modifying the parsing, instrumentation, sandboxing, or indexing components across crates within the APEX project.