skill_author
Author a standard agentskills.io Agent Skill and get back its SKILL.md. A strong skill has: a name in kebab-case (lowercase letters, numbers, single hyphens, ≤64 chars); a description stating WHAT it does AND WHEN to use it, third person, with concrete trigger words (the field agents read to deci...
This record as markdown: /tools/ai-rokha-rokha/skill-author.md
What skill_author does on Rokha
AI agents use skill_author to create or update resources in Rokha, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rokha environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Skill id + folder name. kebab-case, ≤64 chars. |
license | string | — | Optional. A license name or bundled-file reference (e.g. 'MIT'). |
metadata | object | — | Optional. Arbitrary string→string metadata (e.g. {"author":"example-org","version":"1.0"}). |
description | string | Yes | What it does + when to use it. Third person, with trigger words. ≤1024 chars. |
instructions | string | Yes | The Markdown body. Specific + imperative. When-to-use → Instructions → Examples → Guidelines. |
allowed_tools | string | — | Optional. SPACE-separated, least-privilege tool allowlist with optional scoping (e.g. 'Bash(git:*) Read'). Experimental. |
compatibility | string | — | Optional, ≤500 chars. Runtime/environment requirements (e.g. 'Requires Python 3.14+ and uv'). Omit for pure-instruction skills. |
Parameters from the server's own tool schema.
Why skill_author is rated Medium
Creates a new skill document artifact; reversible write operation with moderate blast radius.
From the tool's definition Author a standard agentskills.io Agent Skill and get back its SKILL.md
Attacks that exploit this kind of access
The rule that runs skill_author safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Rokha, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For skill_author, this is the rule to start with:
skill_author stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Rokha, apply this rule, and every skill_author call is checked against it from then on.
Questions about skill_author
Author a standard agentskills.io Agent Skill and get back its SKILL.md. A strong skill has: a name in kebab-case (lowercase letters, numbers, single hyphens, ≤64 chars); a description stating WHAT it does AND WHEN to use it, third person, with concrete trigger words (the field agents read to decide whether to load it); and instructions (the Markdown body), specific + imperative, ideally shaped When-to-use → Instructions → Examples → Guidelines. Optional compatibility (runtime/environment requirements, ≤500 chars — set when the skill needs system packages, a language version, network access, or scripts; omit for pure-instruction skills), allowed_tools (a SPACE-separated, least-privilege allowlist with optional scoping, e.g. 'Bash(git:*) Read'), license (a license name or file reference), and metadata (an object of string→string pairs). Returns the assembled SKILL.md to save as SKILL.md in a folder named after the skill. (In the Rokha UI the same tool fills the human's live builder form.). It is categorised as a Write tool in the Rokha MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
skill_author accepts 7 parameters: name, license, metadata, description, instructions, allowed_tools, compatibility. Required: name, description, instructions. The full parameter table on this page comes from the server's own tool schema.
Register the Rokha MCP server in PolicyLayer and add a rule for skill_author: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Rokha. Nothing to install.
skill_author is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the skill_author rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for skill_author. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
skill_author is provided by the Rokha MCP server (https://rokha.ai/mcp/jsonrpc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Rokha, and thousands of servers like it.
This server
Across the catalogue