Kody weekly: Saved skills now take parameters

Kent C. Dodds · March 20, 2026

Here is what shipped in Kody from March 14 to March 20, 2026. This week we tagged our first two releases, v2026-03-19 and v2026-03-20, and the work centers on the MCP search and execute tools: saved skills you can reuse with different inputs, GitHub GraphQL access, and layouts that work on a phone.

Saved skills take parameters

What shipped

meta_save_skill and meta_update_skill accept an optional parameters list. Each parameter has a name, a description, a type (string, number, boolean, or json), and optional required and default values. When you run the skill with meta_run_skill, you pass values in params, and the saved code receives them as the params variable (or as its first argument). Kody rejects missing required parameters and unknown names, and fills in defaults for anything you leave out. Parameter definitions are stored with the skill and included in its search details, so your agent can see what inputs a skill expects before it runs it.

Why it matters

Until now, a saved skill's inputs lived in its code, so reusing a workflow for a different repository or date range meant editing the skill or saving a near copy. Now one saved skill covers the pattern and your agent supplies the values at run time. That keeps the code you save small, reusable, and easy to find in search.

Example

Save a skill that declares its inputs. This one wraps the new github_graphql capability, which can run mutations, so the skill is saved with matching read_only, idempotent, and destructive flags:

{
	"title": "List open pull requests",
	"description": "Lists the newest open pull requests for a GitHub repository.",
	"keywords": ["github", "pull requests"],
	"code": "async () => codemode.github_graphql({ query: 'query($owner: String!, $name: String!, $count: Int!) { repository(owner: $owner, name: $name) { pullRequests(states: OPEN, first: $count) { nodes { number title } } } }', variables: { owner: params.owner, name: params.repo, count: params.count } })",
	"parameters": [
		{
			"name": "owner",
			"description": "Repository owner",
			"type": "string",
			"required": true
		},
		{
			"name": "repo",
			"description": "Repository name",
			"type": "string",
			"required": true
		},
		{
			"name": "count",
			"description": "How many pull requests to return",
			"type": "number",
			"default": 10
		}
	],
	"read_only": false,
	"idempotent": false,
	"destructive": true
}

Run it with values for this call. count falls back to its default:

{
	"skill_id": "YOUR_SKILL_ID",
	"params": { "owner": "my-org", "repo": "my-repo" }
}

PRs: #19, #21

More updates

MCP: Adds GitHub GraphQL to the coding capabilities. github_graphql sends a query or mutation with optional variables and returns the data and errors from GitHub, and github_graphql_api_docs fetches GitHub's GraphQL reference pages from docs.github.com as markdown. Calls use the GitHub token configured for the server. (#20)
MCP: Makes saved skills easier to run. Each skill hit from search now includes a usage hint with the exact meta_run_skill arguments and a note about optional params, and the meta_run_skill description includes a params example. (#21)
Dashboard: Makes the home page and chat work on phones and tablets. Home feature cards stack into a single column with tighter spacing, and on smaller screens chat shows one panel at a time: the thread list at /chat, then the conversation when you open a thread, driven by the URL. Desktop still opens a thread automatically. (#1, #3)

Fixes

No user-facing fixes this week.

Try it

Save one workflow you repeat often as a skill with meta_save_skill, declare its inputs as parameters, and run it with meta_run_skill. Your agent finds saved skills and capabilities through search; see Search and execute for how the two tools fit together.

Questions or feedback? Join us on the Kody Discord.