Agent skill

Intrinsic Core Debugging

by intrinsic-ai in intrinsic-ai/intrinsic-core

Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…

Apache-2.0Auto-check: notesDevOps & Cloud

Install Intrinsic Core Debugging

skills CLI
$ npx skills add intrinsic-ai/intrinsic-core --skill intrinsic-core-debugging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install intrinsic-ai/intrinsic-core intrinsic-core-debugging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/intrinsic-ai/intrinsic-core.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/intrinsic-core-debugging .claude/skills/intrinsic-core-debugging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
intrinsic-core-debugging
GitHub stars
557
Token cost
~3.8k tokens
SKILL.md length
1,186 words
Files
10 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…

  • Works in 5 steps: Ingress and transport layer… → Kubernetes control plane and container… → Executive and Behavior Tree… → …
  • Tasks that involve Container orchestration
  • SKILL.md covers Architectural triage hierarchy…, Progressive disclosure…, Core CLI and incident… and Paired safety guardrails, plus 3 more sections
  • Calls kubectl and bazel

What it does

Intrinsic Core Debugging is an agent skill from intrinsic-ai/intrinsic-core. Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time control, and hardware modules. Triggers: debug Intrinsic Core failures, gRPC UNIMPLEMENTED, UNAVAILABLE no healthy upstream, Ports not open, Behavior Tree stalls, ICON overruns, multi-world desynchronization, container crashes. Subsystems: INGRESS, ENVOY, KUBERNETES, EXECUTIVE, WORLD, MOTIONPLANNING, ICON, PERCEPTION…

Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `references/assets-and-solutions.md`, `references/bazel.md` and `references/executive-and-behavior-trees.md`).

It sits in DevOps & Cloud, covering Container orchestration, Debugging and gRPC and Protobuf. It works with Kubernetes and gRPC. The repository describes itself as: Intrinsic Core™ provides an open, local runtime, SDK, and hardware agnostic, real-time control framework for industrial robotics. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Container orchestration
  • Tasks that involve Debugging
  • Tasks that involve gRPC and Protobuf

Example prompts

  • “/intrinsic-core-debugging”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Ingress and transport layer (localhost:17080 / Envoy VirtualService): External and inter-pod gRPC traffic routes through Envoy. Named…
  2. Kubernetes control plane and container readiness layer (app-intrinsic-base, app-resources, skills): Services initialize upstream channels…
  3. Executive and Behavior Tree orchestration layer (ExecutiveService): Enforces two-phase operation lifecycle (CreateOperation to stage…
  4. Digital twin and multi-world synchronization layer (ObjectWorldService): Separates static scene ("init_world"), runtime belief state…
  5. Motion planning and real-time control layer (MotionPlannerService & rs-icon): Collision checking over BVH trees (CoalCollisionChecker)…

What it can do on your machine

Read from SKILL.md and the folder at commit 3fd7856. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • kubectl
    • bazel

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use kubectl, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Intrinsic Core Debugging loads about 3.8k tokens when it runs, and up to ~44k if it reads all its reference files. Until then it costs about 182 tokens; SKILL.md has 1,186 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~182
When it runs · the whole SKILL.md, loaded when a task matches
~3.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~44k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteRuns commands with sudoSKILL.md:8
    encies: localhost:17080, inctl, kubectl, sudo coredumpctl, grpc.
  • NoteRuns commands with sudoSKILL.md:19
    `kubectl describe pod` and crashes via `sudo coredumpctl`.
  • NoteRuns commands with sudoSKILL.md:55
    | **Core dump analysis** | `sudo coredumpctl list` and `sudo coredumpctl info <pid>` | Inspects process terminations and
  • NoteRuns commands with sudoSKILL.md:78
    n: Inspect crashed container logs or run sudo coredumpctl info for SIGSEGV tracebacks.
  • NoteRuns commands with sudoSKILL.md:129
    e dumps with `kubectl describe pod` and `sudo coredumpctl`.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from intrinsic-ai/intrinsic-core at commit 3fd7856, republished under its Apache-2.0 licence (© intrinsic-ai). 1,186 words, ~3,752 tokens.

Download SKILL.mdSave it as .claude/skills/intrinsic-core-debugging/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
intrinsic-core-debugging
description
Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time control, and hardware modules. Triggers: debug Intrinsic Core failures, gRPC UNIMPLEMENTED, UNAVAILABLE no healthy upstream, Ports not open, Behavior Tree stalls, ICON overruns, multi-world desynchronization, container crashes. Subsystems: INGRESS, ENVOY, KUBERNETES, EXECUTIVE, WORLD, MOTION_PLANNING, ICON, PERCEPTION. Dependencies: localhost:17080, inctl, kubectl, sudo coredumpctl, grpc. Anti-keywords: inctl service create, inctl skill create, inctl solution list, legacy WORKSPACE, cloud deployments.

Intrinsic Core meta-debugging workflow and component routing

Architectural triage hierarchy and layer isolation

When an anomaly surfaces in an Intrinsic workcell, isolate the originating architectural layer before inspecting application code:

  1. Ingress and transport layer (localhost:17080 / Envoy VirtualService): External and inter-pod gRPC traffic routes through Envoy. Named asset instances (icon, ur_module, camera drivers) require metadata header x-resource-instance-name: <name>. Core platform singletons (ObjectWorldService, ExecutiveService, GeometryService, Operations) route by URI prefix and must omit the instance header (or set exact: intrinsic_runtime).
  2. Kubernetes control plane and container readiness layer (app-intrinsic-base, app-resources, skills): Services initialize upstream channels synchronously before opening serving ports (Ports not open). Multi-container pods (e.g. skills, ml-models-service) can have healthy primary containers alongside crashed inference sidecars (Exit Code 128). Inspect exit codes (137 OOMKilled, 139 SIGSEGV) with kubectl describe pod and crashes via sudo coredumpctl.
  3. Executive and Behavior Tree orchestration layer (ExecutiveService): Enforces two-phase operation lifecycle (CreateOperation to stage, StartOperation to execute). Manages CEL blackboard scoping, default parameter merging, and parallel footprint locks.
  4. Digital twin and multi-world synchronization layer (ObjectWorldService): Separates static scene ("init_world"), runtime belief state ("world"), and simulation ("sim_world"). Preview runs pause belief tracking; reset via inctl world reset --address=localhost:17080.
  5. Motion planning and real-time control layer (MotionPlannerService & rs-icon): Collision checking over BVH trees (CoalCollisionChecker). Hard real-time loop across four phases (rs, proc, ac, exec) over shared memory futexes.

Progressive disclosure reference hub

Read the domain reference guide under references/ matching the failing subsystem before applying remediation:

Reference guideArchitectural domain and diagnostic focusWhen to read it
references/assets-and-solutions.mdServiceManifest, .binpb configs, OCI registry uploads, Ports not open, GPU slicing.Asset installation errors, wire-format parsing errors, or Pending/CrashLoopBackOff pods.
references/executive-and-behavior-trees.mdTwo-phase lifecycle, CEL expressions, blackboard bindings, protobuf 100-recursion limit.Behavior Tree stalls, CEL params variable errors, recovery subtree matching, or tree bloat.
references/geometry-and-math.mdGeometryService, Pose3 keyword args, antipodal quaternions, unscaled millimeter CAD meshes.Missing geometry refs, non-normalized quaternions, pose comparison errors, or slow planning.
references/longrunning-operations.mdgoogle.longrunning.Operations, central operations:8080 proxy, header forwarding, WaitOperation.NOT_FOUND on LRO polling, operation cancellation stalls, or missing asset metadata.
references/motion-planning-and-icon.mdMotionPlannerClient, IK diagnostics, 2π flips, ICON four-phase cycle (rs, proc, ac, exec).compute_ik failures, ICON cycle overruns (exec > 95%), AlreadyExistsError, or hardware faults.
references/perception-and-vision.mdGenICam state machines, Jumbo Frames (9000 MTU), 6DoF pose estimation, Zenoh KV store buffers.Camera register write locks, dropped video frames, GPU inference reload spikes, or calibration.
references/platform-logging-and-status.mdEnvoy routing, /api/http-gateway/ REST prefix, gRPC status taxonomy, 4 MB payload ceilings.Empty UNIMPLEMENTED, HTTP 404 on KV store, 4 MB RESOURCE_EXHAUSTED, or logging sync.
references/world-and-kinematics.mdObjectWorldService multi-world instances ("init_world", "world", "sim_world"), Gazebo lockstep.Stale digital twin poses, world updater paused, robot simulation oscillations, or SDF drift.
references/bazel.md (and intrinsic-core-bazel)Bazel build/test errors, Bzlmod module resolution, pip lockfile updates, and 0-0-2 circuit breakers.Module not found, missing @ai_intrinsic_sdks, requirements lockfile errors, or linker ABI crashes.

Core CLI and incident investigation tools

Execute CLI and Linux inspection commands when triaging a local workcell (--address=localhost:17080):

Investigation taskCommand syntaxOperational contract
Discover subcommandsinctl helpRun inctl help (not inctl --help, which only prints Go logging flags).
Inspect service statesinctl service state list --address=localhost:17080 --output=jsonOutput JSON reveals raw STATE_CODE_ERROR masked by tabular summary strings.
Map running assetsinctl asset instance list --address=localhost:17080Maps active resource instance names (e.g. icon, ur_module) to asset IDs.
Inspect ICON statusinctl icon status --instance_name=icon --address=localhost:17080--instance_name=icon is mandatory for Envoy x-resource-instance-name routing.
Clear hardware faultsinctl icon clear-faults --instance_name=icon --address=localhost:17080Resets module faults safely without tearing down shared-memory futexes.
Reset multi-world stateinctl world reset --address=localhost:17080Synchronizes belief/sim worlds to "init_world" and unpauses frozen world updater.
Stage vs. run processinctl process set --server=localhost:17080Note --server flag; only stages CreateOperation. Call StartOperation to run.
Container status / crashkubectl describe pod <pod> -n <namespace>Exposes exit codes (128 start error, 137 OOMKilled, 139 SIGSEGV) across sidecars.
Targeted log filteringkubectl logs -n <namespace> <pod> -c <container> --tail=200Filters logs by specific container.
Core dump analysissudo coredumpctl list and sudo coredumpctl info <pid>Inspects process terminations and stack traces from crashed C++ binaries.
Show full SKILL.md (518 more words)Show less

Paired safety guardrails

  1. Ingress metadata routing headers: Attach x-resource-instance-name: <name> when invoking named asset instances (e.g., --instance_name=icon on inctl icon), and omit it when querying core platform singletons (ObjectWorldService, MotionPlannerService, ExecutiveService, Operations); do not supply asset instance headers to platform services, which causes Envoy to return an empty UNIMPLEMENTED status code.
  2. Command-line flag syntax and discovery: Run inctl help or inctl <subcommand> --help to discover subcommands, supply --address=localhost:17080 for asset/service/icon/world subcommands, and use --server=localhost:17080 for process commands (do not run inctl --help, which intercepts Go logging flags without listing subcommands, nor pass --address to inctl process).
  3. Behavior Tree execution lifecycle: Invoke StartOperation or call executive.run() to start staged operations (do not assume inctl process set executes the tree; it only stages the definition via CreateOperation).
  4. Hardware module fault remediation: Clear controller and hardware faults via inctl icon clear-faults --instance_name=icon --address=localhost:17080 after physical safety interlocks are cleared (do not restart hardware module pods directly, which destroys shared memory segments and futexes while controller processes remain attached).
  5. Service configuration wire format: Serialize configuration protobufs inside google.protobuf.Any and supply binary .binpb files to inctl service add --config=<path> (do not pass .textproto files, which fail with invalid wire-format parsing errors).

Diagnostic decision tree for Intrinsic Core failure modes

[Anomaly detected on workcell]
  │
  ├─► [Symptom: rpc error: code = Unimplemented desc = (empty description)]
  │     ├─► Precondition: Client issued gRPC request or inctl command across localhost:17080.
  │     ├─► Diagnostic check: Inspect x-resource-instance-name header against VirtualService routes.
  │     └─► Targeted action: Supply --instance_name=<name> for asset instances, or omit header for core platform services.
  │
  ├─► [Symptom: rpc error: code = Unavailable desc = no healthy upstream]
  │     ├─► Precondition: VirtualService route matched, but target pod or sidecar is not serving.
  │     ├─► Diagnostic check: Run kubectl describe pod <pod> -n <ns>; check container exit codes (128, 137, 139).
  │     └─► Targeted action: Inspect crashed container logs or run sudo coredumpctl info for SIGSEGV tracebacks.
  │
  ├─► [Symptom: Ports not open: <service>.<namespace>:8080]
  │     ├─► Precondition: Solution startup health gate timed out before target service bound port 8080.
  │     ├─► Diagnostic check: Trace synchronous upstream gRPC channels (e.g. executive -> simulation_service:8088 -> gzserver).
  │     └─► Targeted action: Resolve upstream dependency stall (e.g. Gazebo mesh loading) before checking target container.
  │
  ├─► [Symptom: Behavior Tree staged via inctl process set does not execute]
  │     ├─► Precondition: Tree staged in ExecutiveService via CreateOperation.
  │     ├─► Diagnostic check: Verify operation state via ExecutiveService/ListOperations.
  │     └─► Targeted action: Issue ExecutiveService/StartOperation or call executive.run() to trigger execution.
  │
  ├─► [Symptom: ICON control loop overrun: Long duration between read_status_calls]
  │     ├─► Precondition: Real-time loop (500 Hz / 1 kHz) missed deadline on isolated real-time core.
  │     ├─► Diagnostic check: Inspect rs-icon logs; compare futex sleep (exec) vs. computation (rs + proc + ac).
  │     └─► Targeted action: If exec > 95%, resolve host CPU preemption, E-core scheduling, or CFS quota throttling.
  │
  ├─► [Symptom: Gazebo simulation ignores world edits or live robot poses freeze]
  │     ├─► Precondition: Behavior Tree executed in simulation preview or multi-world desynchronized.
  │     ├─► Diagnostic check: Run inctl world reset --address=localhost:17080 or inspect world updater paused state.
  │     └─► Targeted action: Reset worlds via inctl world reset or supply start_from_world_state=worlds.EditWorldId.BELIEF.
  │
  ├─► [Symptom: failed to upload image: failed to dial "/run/containerd/containerd.sock": connect: connection refused]
  │     ├─► Precondition: inctl asset install or sideloading attempted across localhost:17127 / localhost:17080.
  │     ├─► Diagnostic check: Confirm failure is on backend k3s host daemon, NOT in local client environment.
  │     └─► Targeted action: Stop after at most 2 attempts. Never debug local /run or proxy sockets; verify hermetically via bazel build and bazel test.
  │
  └─► [Symptom: grpc: received message larger than max (X vs. 4194304)]
        ├─► Precondition: Mesh, point cloud, or complex BehaviorTree transferred across default channel.
        ├─► Diagnostic check: Check transfer payload size against default 4 MB ceiling.
        └─► Targeted action: Configure channel options with [("grpc.max_receive_message_length", -1)].

System 2 reflection and circuit breaker checkpoints

Pre-execution reflection checkpoint

Before executing mutations or restart sequences on a failing workcell:

  1. Identify fault layer: Determine whether failure originates in ingress, container readiness, Executive, ObjectWorld, or ICON.
  2. Verify routing headers: Ensure x-resource-instance-name is attached only for asset instances and omitted for core singletons.
  3. Verify container exit states: Run kubectl describe pod to distinguish OOM (137), crash (139), or sidecar failure (128).
  4. Verify world synchronization: Confirm "world" and "sim_world" are aligned before diagnosing motion planning errors.
Anti-thrashing circuit breaker
  • Retry budget: Limit diagnostic queries and retries to <= 3 attempts with exponential backoff (1s, 2s, 4s).
  • Trip condition: If three successive checks fail with identical status codes (UNAVAILABLE or UNIMPLEMENTED), halt command execution. Escalate from application logic to upstream dependency inspection (Ports not open dependency chains or host CPU CFS throttling).
  • Backend containerd socket and OCI upload circuit breaker: When inctl asset install or sideloading fails with failed to dial "/run/containerd/containerd.sock": connect: connection refused or connection refused on localhost:17127, cap retries at <= 2 attempts. The containerd socket and mount reside in k3s on the cluster host, NOT in the local client environment (e.g. Bubblewrap sandbox). Do NOT run find /run or attempt to proxy /run/containerd/containerd.sock. Immediately halt cluster upload attempts and fall back to verifying hermetic Bazel build and test targets locally (bazel build //..., bazel test //...).

Verification criteria

  • Layer isolated: Identified originating fault layer using the five-tier architectural triage hierarchy.
  • Ingress headers verified: Applied x-resource-instance-name for asset instances and omitted for platform singletons.
  • Container health checked: Verified pod exit codes and core dumps with kubectl describe pod and sudo coredumpctl.
  • Deterministic CLI used: Supplied --address=localhost:17080 for asset/service/icon/world and --server=localhost:17080 for process.
  • multi-world synchronized: Verified "world" and "sim_world" alignment via inctl world reset before debugging motion.
  • Circuit breaker respected: Halted repetitive action loops after 3 attempts and inspected upstream dependencies.

© intrinsic-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in .agents/skills/intrinsic-core-debugging of intrinsic-ai/intrinsic-core.

  • SKILL.md
  • references/assets-and-solutions.md
  • references/bazel.md
  • references/executive-and-behavior-trees.md
  • references/geometry-and-math.md
  • references/longrunning-operations.md
  • references/motion-planning-and-icon.md
  • references/perception-and-vision.md
  • references/platform-logging-and-status.md
  • references/world-and-kinematics.md

Open the folder on GitHubat commit 3fd7856

Compare with similar skills

Intrinsic Core Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Intrinsic Core Debugging compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intrinsic Core Debugging this skillintrinsic-ai/intrinsic-core557—~3.8kAutomated safety check: NotesApache-2.0
Kubeshark KFL2 Filter Referencekubeshark/kubeshark12k—~3.6kAutomated safety check: PassApache-2.0
Aks Deployment Skilltimothywarner/chatgptclass143—~916Automated safety check: PassCustom licence
Ocioracle/skills876—~2.4kAutomated safety check: PassUPL-1.0
Platform Engineeringmagnus919/agent-skills116—~2.4kAutomated safety check: PassMIT
Frontend Forge Extension Operationskubesphere/kubesphere17k—~3.2kAutomated safety check: PassCustom licence

Similar skills

  • Syntax reference for KFL2, the CEL-based display filter language used to search Kubernetes network traffic captured by Kubeshark, loaded before any filter is written.

    12k GitHub stars~3.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Aks Deployment Skill

    timothywarner/chatgptclass

    Deploy and operate workloads on Azure Kubernetes Service (AKS) the safe way.

    143 GitHub stars~916 tokensUpdated 20 days ago
    DevOps & CloudAuto-check passed
  • Oci

    oracle/skills

    Official

    Oracle Cloud Infrastructure guidance for designing, operating, and troubleshooting OCI services, including OCI Kubernetes Engine (OKE), OCI Internet of Things Platform, OCI Functions deployment and…

    876 GitHub stars~2.4k tokensUpdated 3 days ago
    DevOps & CloudAuto-check passed
  • Platform Engineering

    magnus919/agent-skills

    A skill your agent uses when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability, or when…

    116 GitHub stars~2.4k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.

    17k GitHub stars~3.2k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed
  • Frontend Forge FI Operations

    kubesphere/kubesphere

    Operates FrontendIntegration resources and the frontend-forge extension with kubectl: create from YAML, update, enable, disable, delete, inspect and troubleshoot builds.

    17k GitHub stars~1.3k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check passed

More from intrinsic-ai/intrinsic-core

All 9 skills in this repo
  • Intrinsic Core API Overview

    intrinsic-ai/intrinsic-core

    Intrinsic Core gRPC service selection, Envoy x-resource-instance-name routing, and progressive disclosure hub across ObjectWorldService, MotionPlannerService, ICON, cameras, KVStore, and platform…

    557 GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Intrinsic Core Robot Motion

    intrinsic-ai/intrinsic-core

    Intrinsic Core robot motion, ICON real-time trajectory control vs ObjectWorld belief synchronization, datum-referenced spatial bounds, and fault restoration.

    557 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • Intrinsic Core Solution Building

    intrinsic-ai/intrinsic-core

    Intrinsic Solution Building Library (SBL) Python SDK guide for connecting to workcells, composing Behavior Trees, querying/mutating ObjectWorld frames, binding equipment resources, and orchestrating…

    557 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Intrinsic Core Concepts

    intrinsic-ai/intrinsic-core

    Intrinsic Core zero-cloud architecture, core primitives (Assets, Services, Skills, Solutions, ICON), CLI inspection commands, and workspace search rules.

    557 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Intrinsic Core Service Authoring

    intrinsic-ai/intrinsic-core

    Intrinsic Core microservice authoring, ServiceManifest definitions (realspec vs simspec), RuntimeContext port bindings (gRPC port 1 vs HTTP port 7), SIGTERM lifecycle handling, and .binpb sideloading.

    557 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Intrinsic Core Skill Authoring

    intrinsic-ai/intrinsic-core

    Authoring Intrinsic Core robot skills and stateless behavior tree leaf action nodes.

    557 GitHub stars~3k tokensUpdated today
    Auto-check passed

Works with

Questions about Intrinsic Core Debugging

What does Intrinsic Core Debugging do?

Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…. Intrinsic Core Debugging is an agent skill from intrinsic-ai/intrinsic-core. Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time control, and hardware modules.

When should I use Intrinsic Core Debugging?

Intrinsic Core Debugging fits situations like: tasks that involve Container orchestration; tasks that involve Debugging; tasks that involve gRPC and Protobuf.

How do I install Intrinsic Core Debugging in Claude Code?

Run `npx skills add intrinsic-ai/intrinsic-core --skill intrinsic-core-debugging -a claude-code`. Or copy the skill folder (.agents/skills/intrinsic-core-debugging in intrinsic-ai/intrinsic-core) into .claude/skills/intrinsic-core-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Intrinsic Core Debugging in Codex?

Run `npx skills add intrinsic-ai/intrinsic-core --skill intrinsic-core-debugging -a codex`. Or copy the skill folder (.agents/skills/intrinsic-core-debugging in intrinsic-ai/intrinsic-core) into .agents/skills/intrinsic-core-debugging in your project. Codex loads it when a task matches its description.

Can I use Intrinsic Core Debugging in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add intrinsic-ai/intrinsic-core --skill intrinsic-core-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intrinsic-core-debugging, .gemini/skills/intrinsic-core-debugging, .github/skills/intrinsic-core-debugging and .opencode/skills/intrinsic-core-debugging in your project.

What does Intrinsic Core Debugging need to run?

Going by SKILL.md and its folder, Intrinsic Core Debugging needs the command-line tools its instructions call (kubectl and bazel).

Does Intrinsic Core Debugging access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Intrinsic Core Debugging safe to install?

Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Intrinsic Core Debugging use?

Intrinsic Core Debugging is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Intrinsic Core Debugging use?

About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 40k tokens, read only when the agent opens those files.

What are the alternatives to Intrinsic Core Debugging?

Skills that share tags, products or a category with Intrinsic Core Debugging: Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Aks Deployment Skill (timothywarner/chatgptclass, 143 stars), Oci (oracle/skills, 876 stars) and Platform Engineering (magnus919/agent-skills, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intrinsic Core Debugging?

intrinsic-ai (a GitHub organization) maintains it in intrinsic-ai/intrinsic-core, which has 557 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 9, 2026.

Source: intrinsic-ai/intrinsic-core on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.