Agent skill

Intrinsic Core API Overview

by intrinsic-ai in 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…

Apache-2.0Auto-check passedBackend & APIs

Install Intrinsic Core API Overview

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

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

GitHub CLI
$ gh skill install intrinsic-ai/intrinsic-core intrinsic-core-api-overview --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-api-overview .claude/skills/intrinsic-core-api-overview && 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-api-overview
GitHub stars
562
Token cost
~3.4k tokens
SKILL.md length
792 words
Files
8 (incl. references)
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

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

  • Works in 5 steps: Envoy ingress routing headers: Attach… → Context handle access across execution… → Spatial pose construction parameter… → …
  • Tasks that involve gRPC and Protobuf
  • SKILL.md covers Progressive disclosure…, How to communicate with an…, Paired safety guardrails and Diagnostic decision tree for…, plus 2 more sections
  • Calls bazel and kubectl

What it does

Intrinsic Core API Overview is an agent skill from 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 APIs. Triggers: select Intrinsic Core API, gRPC routing, Envoy ingress, x-resource-instance-name, asset instance vs platform service, coordinate frame mutation, multi-world lifecycle, trajectory planning, real-time control, camera capture, KVStore. Subsystems: INGRESS, ENVOY, WORLD, MOTIONPLANNING, ICON, PERCEPTION…

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `references/assets-and-solutions.md`, `references/geometry-and-math.md` and `references/longrunning-operations.md`).

It sits in Backend & APIs, covering gRPC and Protobuf, Cloud networking and Container orchestration. It works with gRPC and Kubernetes. 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 gRPC and Protobuf
  • Tasks that involve Cloud networking
  • Tasks that involve Container orchestration

Example prompts

  • “/intrinsic-core-api-overview”

Requirements

  • Python 3

Workflow steps

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

  1. Envoy ingress routing headers: Attach x-resource-instance-name: metadata header when calling deployed asset instances (e.g. icon…
  2. Context handle access across execution phases: Read leased equipment connections via context.resource_handles[""] strictly within…
  3. Spatial pose construction parameter ordering: Supply explicit keyword arguments when instantiating Pose3(rotation=..., translation=...)…
  4. Multi-world transformation scoping and cleanup: Specify node_to_update when invoking update_transform across non-neighboring nodes, and…
  5. CLI addressing and subcommand selection: Supply --address=localhost:17080 for commands (run inctl service state list…

What it can do on your machine

Read from SKILL.md and the folder at commit 0221644. 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:

    • bazel
    • kubectl

    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 API Overview loads about 3.4k tokens when it runs, and up to ~83k if it reads all its reference files. Until then it costs about 195 tokens; SKILL.md has 792 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 0221644, republished under its Apache-2.0 licence (© intrinsic-ai). 792 words, ~3,400 tokens.

Download SKILL.mdSave it as .claude/skills/intrinsic-core-api-overview/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
intrinsic-core-api-overview
description
Intrinsic Core gRPC service selection, Envoy x-resource-instance-name routing, and progressive disclosure hub across ObjectWorldService, MotionPlannerService, ICON, cameras, KVStore, and platform APIs. Triggers: select Intrinsic Core API, gRPC routing, Envoy ingress, x-resource-instance-name, asset instance vs platform service, coordinate frame mutation, multi-world lifecycle, trajectory planning, real-time control, camera capture, KVStore. Subsystems: INGRESS, ENVOY, WORLD, MOTION_PLANNING, ICON, PERCEPTION, EXECUTIVE, KVSTORE. Dependencies: localhost:17080, grpc, intrinsic.util.grpc, ObjectWorldClient, MotionPlannerClient, icon_api. Anti-keywords: inctl service create, inctl skill create, inctl solution list, kubectl scale, legacy WORKSPACE.

Intrinsic Core API overview and progressive disclosure hub

Progressive disclosure reference hub

Read the domain reference under references/ matching your task before writing gRPC or Python SDK code:

Reference guideDomain and gRPC / SDK surfaceWhen to read it
references/assets-and-solutions.mdInstalledAssets, AssetDeploymentService, intrinsic_proto.storage.StorageService, ArtifactCatalogService, intrinsic_proto.solution.v1.SolutionServiceCommunicate with an Intrinsic asset vs. an Intrinsic Core platform service, install assets, or manage solution lifecycles.
references/world-and-kinematics.mdObjectWorldService (intrinsic_proto.world.ObjectWorldService/CloneWorld), intrinsic_proto.kinematics.KinematicsService, FrameCalibrationService, SkeletonRead or mutate digital twin frames/transforms (node_to_update, ReparentObject). Manage initial vs. belief vs. simulation worlds.
references/geometry-and-math.mdintrinsic_proto.geometry.GeometryService, Pose3, Rotation3, Octree, OrientedBoundingBox, RenderableConstructing spatial poses (Pose3(rotation=..., translation=...)), converting quaternions, registering meshes, and collision footprints.
references/motion-planning-and-icon.mdMotionPlannerService (MotionPlannerClient), IconApi (icon_api.Client)Move robot in real time or execute trajectory. Plan collision-free path or IK, settling (intrinsic.is_settled).
references/perception-and-hardware.mdCameraService, intrinsic_proto.perception.v1.PoseEstimationService, CalibrationService, intrinsic_proto.gripper.GenericGripper, GPIOServiceCapture camera images or estimate poses (grpc.max_receive_message_length), optical frames (camera_t_target), calibration, and gripper/GPIO.
references/longrunning-operations.mdgoogle.longrunning.Operations, central LRO proxy, intrinsic_proto.executive.ExecutiveService, intrinsic_proto.conductor.ConductorServicePolling long-running operations (WaitOperation vs. GetOperation), handling LRO proxy routing, and inspecting executive operations.
references/platform-logging-and-status.mdintrinsic_proto.logging.DataLogger, BagPackager, KVStore, SimulationService, ExtendedStatusShare state via KV store or executive blackboard, emitting structured logs, local telemetry, and simulation resets.
../intrinsic-core-bazel/SKILL.mdBzlmod module configuration, canonical SDK dependencies (@ai_intrinsic_sdks), protobuf targets, and hermetic build rules.Declaring dependencies for any Intrinsic gRPC service or SDK module in BUILD files.

How to communicate with an Intrinsic asset vs. an Intrinsic Core platform service

External and inter-service gRPC traffic routes through the Envoy ingress gateway (localhost:17080 externally or istio-ingressgateway.app-ingress.svc.cluster.local:80 inside Kubernetes pods). Envoy uses two distinct routing mechanisms depending on target multiplicity:

DimensionIntrinsic asset (service instance)Intrinsic Core platform service (workcell singleton)
ExamplesCustom microservices, camera drivers (basler_camera), grippers, hardware modules (ur_module, icon).ObjectWorldService, MotionPlannerService, ExecutiveService, Operations, SystemServiceState.
Envoy routing keyRequires x-resource-instance-name: <instance_name> metadata header on every RPC.Routed by gRPC URI path prefix (/intrinsic_proto.<pkg>.<Service>/<Method>). Omit instance header.
Connection modeUse connection.ConnectionParams(address=..., instance_name="<name>", header="x-resource-instance-name").Plain grpc.insecure_channel(address) passed directly to the generated gRPC service stub.
Inside Skill.execute()Read context.resource_handles["<slot>"] and extract handle.connection_info.grpc.Access context.object_world and context.motion_planner directly (context.grpc_channel does not exist).
Inside Skill.preview()Hardware handles not leased; use context.get_object_for_equipment("<slot>").context.object_world is read-only; record speculative changes via context.record_world_update(...).
python
import os
from typing import Any
import grpc
from intrinsic.util.grpc import connection, interceptor
from intrinsic.world.proto import object_world_service_pb2_grpc
from intrinsic.world.python import object_world_client

_CHANNEL_OPTIONS = [("grpc.max_receive_message_length", -1)]


def resolve_workcell_ingress_address(default_address: str = "localhost:17080") -> str:
  """Resolves in-cluster Envoy ingress DNS when executing inside a Kubernetes pod."""
  if "KUBERNETES_SERVICE_HOST" in os.environ:
    return "istio-ingressgateway.app-ingress.svc.cluster.local:80"
  return default_address


def connect_to_asset_instance(
    instance_name: str, address: str | None = None
) -> grpc.Channel:
  """Creates a gRPC channel routed to a specific named Intrinsic asset instance."""
  params = connection.ConnectionParams(
      address=address or resolve_workcell_ingress_address(),
      instance_name=instance_name,
      header="x-resource-instance-name",
  )
  base = grpc.insecure_channel(params.address, options=_CHANNEL_OPTIONS)
  return grpc.intercept_channel(
      base, interceptor.HeaderAdderInterceptor(params.headers)
  )


def create_channel_from_resource_handle(handle: Any) -> grpc.Channel:
  """Extracts connection_info.grpc from a leased ResourceHandle message."""
  info = handle.connection_info.grpc
  return connect_to_asset_instance(
      instance_name=info.server_instance,
      address=info.address or resolve_workcell_ingress_address(),
  )


def connect_to_platform_world_service(
    address: str | None = None, world_id: str = "world"
) -> object_world_client.ObjectWorldClient:
  """Connects directly to the singleton ObjectWorldService without instance headers."""
  channel = grpc.insecure_channel(
      address or resolve_workcell_ingress_address(), options=_CHANNEL_OPTIONS
  )
  stub = object_world_service_pb2_grpc.ObjectWorldServiceStub(channel)
  return object_world_client.ObjectWorldClient(world_id=world_id, stub=stub)

Paired safety guardrails

  1. Envoy ingress routing headers: Attach x-resource-instance-name: <instance_name> metadata header when calling deployed asset instances (e.g. icon, basler_camera, custom services); do not pass x-resource-instance-name to core platform runtime services (ObjectWorldService, GeometryService, ExecutiveService, Operations), as mismatched instance headers cause Istio to reject requests with UNIMPLEMENTED.
  2. Context handle access across execution phases: Read leased equipment connections via context.resource_handles["<slot>"] strictly within Skill.execute(), and query proxy objects via context.get_object_for_equipment("<slot>") in Skill.preview() (do not attempt to access context.resource_handles during preview(), nor access non-existent context.grpc_channel).
  3. Spatial pose construction parameter ordering: Supply explicit keyword arguments when instantiating Pose3(rotation=..., translation=...) (do not pass positional arguments, which silently map translation vectors to rotation quaternions and cause ValueError: Quaternion is not normalized).
  4. Multi-world transformation scoping and cleanup: Specify node_to_update when invoking update_transform across non-neighboring nodes, and manage speculative worlds in a try...finally block with DeleteWorld (do not pass custom strings to cloned_world_id on CloneWorld; supply cloned_world_hint="sandbox" and let the server generate the ID).
  5. CLI addressing and subcommand selection: Supply --address=localhost:17080 for commands (run inctl service state list --address=localhost:17080 and inctl asset instance list --address=localhost:17080; explore options via inctl help and inctl --help); do not run un-scoped service or solution commands without state flags.
Show full SKILL.md (244 more words)Show less

Diagnostic decision tree for Intrinsic Core API workflows

[gRPC / CLI error during Intrinsic Core API workflow]
  │
  ├─► [Symptom: rpc error: code = Unimplemented desc = (empty description)]
  │     └─► Cause: Missing x-resource-instance-name header on asset instance or invalid header on platform service.
  │     └─► Action: Add x-resource-instance-name for asset instances, or omit header for core platform services.
  │
  ├─► [Symptom: rpc error: code = Unavailable desc = no healthy upstream]
  │     └─► Cause: Target container crashed (SIGSEGV), inference sidecar exited (128), or CFS CPU throttling.
  │     └─► Action: Check kubectl describe pod in app-intrinsic-app-chart; verify upstream service dependencies.
  │
  ├─► [Symptom: grpc: received message larger than max (X vs 4194304)]
  │     └─► Cause: Mesh or point cloud transfer exceeded default 4 MB gRPC receive message ceiling.
  │     └─► Action: Configure channel with [("grpc.max_receive_message_length", -1)] or 64 MB limit.
  │
  ├─► [Symptom: KeyError: 'resource_handles' or AttributeError during Skill.preview()]
  │     └─► Cause: Attempting to access live hardware resource handles during preview phase.
  │     └─► Action: Use context.get_object_for_equipment("<slot>") and record updates via context.record_world_update().
  │
  ├─► [Symptom: INVALID_ARGUMENT: node_to_update is required when updating non-neighboring nodes]
  │     └─► Cause: update_transform invoked across multi-hop transform path without disambiguating target node.
  │     └─► Action: Pass node_to_update=target_node explicitly to update_transform().
  │
  ├─► [Symptom: HTTP 404 Not Found on REST gateway /api/kvstore/stores/...]
  │     └─► Cause: Envoy gateway missing mandatory /api/http-gateway/ path prefix rewrite.
  │     └─► Action: Prepend /api/http-gateway to the request path (/api/http-gateway/api/kvstore/...).
  │
  └─► [Symptom: failed to upload image: failed to dial "/run/containerd/containerd.sock": connect: connection refused]
        └─► Cause: Backend artifacts-deployment pod in k3s cannot reach host containerd socket.
        └─► Action: Cap at <= 2 attempts; do not inspect local /run or proxy socket; verify build/test hermetically with bazel.

System 2 reflection and circuit breaker checkpoints

  • Pre-execution reflection: Before calling APIs or authoring code, verify: (1) routing target (x-resource-instance-name header for assets vs. direct URI path for singletons); (2) execution phase (resource_handles in execute() vs. get_object_for_equipment in preview()); (3) message length (options=[("grpc.max_receive_message_length", -1)]); (4) explicit keyword arguments on Pose3(rotation=..., translation=...).
  • Anti-thrashing circuit breaker: Cap operation/status polling at <= 3 retries (backoff: 1s, 2s, 4s). If receiving repeated empty UNIMPLEMENTED or UNAVAILABLE: no healthy upstream, halt redialing; inspect Envoy routing headers and pod container exit codes (kubectl describe pod) instead.
  • Backend containerd socket and OCI upload circuit breaker: Cap asset installation retries at <= 2 attempts. If inctl asset install or sideloading fails with containerd socket connection refused (/run/containerd/containerd.sock or localhost:17127), halt cluster upload attempts immediately. The failure is on the backend k3s daemon on the cluster host, NOT in the local client environment (e.g. Bubblewrap sandbox). Do NOT search for sockets with find /run, inspect local /run sockets, or attempt to proxy /run/containerd/containerd.sock. Verify hermetically with bazel build //... and bazel test //....

Verification criteria

  • Ingress routing verified: Attached x-resource-instance-name header for asset instances; omitted header for platform services.
  • Clean operation polling: Polled google.longrunning.Operations on a headerless channel without leaking instance names.
  • Phase-appropriate context: Read context.resource_handles strictly in execute(); used get_object_for_equipment in preview().
  • Payload options set: Configured grpc.max_receive_message_length = -1 for large perception or geometry transfers.
  • Multi-world safety: Managed cloned worlds inside try...finally with DeleteWorld; passed node_to_update on non-neighbor transforms.

© 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 7 other files (references) in .agents/skills/intrinsic-core-api-overview of intrinsic-ai/intrinsic-core.

  • SKILL.md
  • references/assets-and-solutions.md
  • references/geometry-and-math.md
  • references/longrunning-operations.md
  • references/motion-planning-and-icon.md
  • references/perception-and-hardware.md
  • references/platform-logging-and-status.md
  • references/world-and-kinematics.md

Open the folder on GitHubat commit 0221644

Compare with similar skills

Intrinsic Core API Overview 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 API Overview compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Intrinsic Core API Overview this skillintrinsic-ai/intrinsic-core562—~3.4kAutomated safety check: PassApache-2.0
Domain Cloud Nativemoeru-ai/auv1001 repos~1kAutomated safety check: PassApache-2.0
Kubeshark KFL2 Filter Referencekubeshark/kubeshark12k—~3.6kAutomated safety check: PassApache-2.0
Performing Cloud Native Forensics With Falcomukul975/Anthropic-Cybersecurity-Skills34k—~635Automated safety check: PassApache-2.0
Kratos Developmentaide-family/moon253—~1.5kAutomated safety check: PassNone
Dotnet APInovotnyllc/dotnet-artisan232—~1.6kAutomated safety check: PassMIT

Similar skills

  • A skill your agent uses when building cloud-native apps. An agent skill from moeru-ai/auv.

    100 GitHub starsUsed in 1 repo~1k tokens
    DevOps & CloudAuto-check passed
  • 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 yesterday
    DevOps & CloudAuto-check passed
  • Performing Cloud Native Forensics With Falco

    mukul975/Anthropic-Cybersecurity-Skills

    Uses Falco YAML rules for runtime threat detection in containers and Kubernetes, monitoring syscalls for shell spawns, file tampering, network anomalies, and privilege escalation.

    34k GitHub stars~635 tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Kratos Development

    aide-family/moon

    Develops Go microservices with Kratos v2 following official design philosophy, DDD/Clean Architecture layout, Protobuf API, error/config/middleware patterns, and observability.

    253 GitHub stars~1.5k tokensUpdated 3 mo ago
    Backend & APIsAuto-check passed
  • Dotnet API

    novotnyllc/dotnet-artisan

    Builds ASP.NET Core APIs, EF Core data access, gRPC, SignalR, and backend services with middleware, security (OAuth, JWT, OWASP), resilience, messaging, OpenAPI, .NET Aspire, Semantic Kernel…

    232 GitHub stars~1.6k tokensUpdated 3 days ago
    Backend & APIsAuto-check passed
  • Doca Dms

    NVIDIA/skills

    Official

    Operate NVIDIA DOCA Management Service (dmsd + dmspe) on a BlueField, Arm/x86 host, or Kubernetes pod: choose deployment and authentication, configure -allowedusers and dmsgroup, use gNMI…

    3.6k GitHub stars~2.8k tokensUpdated yesterday
    Backend & APIsAuto-check passed

More from intrinsic-ai/intrinsic-core

All 9 skills in this repo
  • Intrinsic Core Debugging

    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…

    562 GitHub stars~3.8k tokensUpdated today
    Auto-check: notes
  • 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.

    562 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…

    562 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.

    562 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.

    562 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.

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

Works with

Categories

Questions about Intrinsic Core API Overview

What does Intrinsic Core API Overview do?

Intrinsic Core gRPC service selection, Envoy x-resource-instance-name routing, and progressive disclosure hub across ObjectWorldService, MotionPlannerService, ICON, cameras, KVStore, and platform…. Intrinsic Core API Overview is an agent skill from 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 APIs.

When should I use Intrinsic Core API Overview?

Intrinsic Core API Overview fits situations like: tasks that involve gRPC and Protobuf; tasks that involve Cloud networking; tasks that involve Container orchestration.

How do I install Intrinsic Core API Overview in Claude Code?

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

How do I install Intrinsic Core API Overview in Codex?

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

Can I use Intrinsic Core API Overview 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-api-overview -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-api-overview, .gemini/skills/intrinsic-core-api-overview, .github/skills/intrinsic-core-api-overview and .opencode/skills/intrinsic-core-api-overview in your project.

What does Intrinsic Core API Overview need to run?

Going by SKILL.md and its folder, Intrinsic Core API Overview needs the command-line tools its instructions call (bazel and kubectl). Our summary lists: Python 3.

Does Intrinsic Core API Overview 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 API Overview safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Intrinsic Core API Overview use?

Intrinsic Core API Overview 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 API Overview use?

About 3.4k tokens (SKILL.md is roughly 14k 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 79k tokens, read only when the agent opens those files.

What are the alternatives to Intrinsic Core API Overview?

Skills that share tags, products or a category with Intrinsic Core API Overview: Domain Cloud Native (moeru-ai/auv, 100 stars), Kubeshark KFL2 Filter Reference (kubeshark/kubeshark, 12k stars), Performing Cloud Native Forensics With Falco (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Kratos Development (aide-family/moon, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intrinsic Core API Overview?

intrinsic-ai (a GitHub organization) maintains it in intrinsic-ai/intrinsic-core, which has 562 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 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.