Skip to main content
Glama
Sign In
kernl

kernl

by fastslack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

kernel_skill_load

Loads the step-by-step playbook for an attached procedural skill when a user request matches it, so the agent can read instructions before acting.

Instructions

Load the full body of a procedural skill the agent has attached. Call this when a user request matches a skill listed in the system_prompt's 'Available skills' section, to read the step-by-step playbook before acting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "kernel_skill_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNoA reference file the skill ships (a path from its 'Files in this skill' list). Omit to load the playbook itself.
slugYesSkill slug — must be one listed in the agent's Available skills index
queryNoOnly for a long list file (a lessons log): what to look for in it. Omitted: what this run is about. "*": the whole file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description carries the full burden; it does disclose that the call returns the full body/step-by-step playbook, which is meaningful behavioral context. However, it says nothing about side effects, idempotency, error behavior when the slug is not attached, or the shape of the returned content (no output schema exists to cover this).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the identifying action front-loaded and the trigger condition following immediately. Nothing is repeated from the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple content-retrieval tool with fully documented parameters, no annotations, and no output schema, the description covers what it does and when to invoke it adequately. The remaining gap is what the returned payload looks like and how failures surface, which is a minor but real omission given no output schema exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter (file, slug, query) has a substantive description in the schema, so the structured data does the heavy lifting. The prose only adds the notion of loading "the full body" or the playbook itself, which is consistent with but not beyond the schema's own explanation of omitting `file`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ("Load the full body of a procedural skill") plus a scoping qualifier ("the agent has attached"), which is clearly distinct from index-listing siblings like kernel_agents_get_skills. An agent can tell that this retrieves skill content rather than listing or managing skills.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the trigger condition precisely: call it when a user request matches a skill in the system prompt's 'Available skills' section, and it adds the sequencing constraint "before acting." It stops short of naming explicit alternatives or exclusion cases (e.g., what to do when no skill matches), so it is clear context rather than a full when/when-not map.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools