Skill

A Skill is a Markdown file that collects the steps and cautions for working with genko.me. You place it in your project with the CLI, and a supported coding agent can read it.

Check the contents

To check before anything is written, run this in the project root.

npx @genko-me/cli skill --print

The text is written in English for agents. It mainly covers initial setup, schema sync, the typed client, handling API keys, and where to find the documentation.

Place it in your project

npx @genko-me/cli skill

This creates the following file.

.claude/skills/genko-me/SKILL.md

The CLI places a Skill in the Claude Code format. Other tools don't necessarily load this location automatically. Match the way your tool loads Skills, or point it at the file explicitly.

For agents without the CLI, the same Skill is listed at https://genko.me/.well-known/agent-skills/index.json and can be read at https://genko.me/.well-known/agent-skills/genko-me/SKILL.md. The content is the same as what the CLI places.

What to have it use

For example, you can ask like this.

Follow the genko-me Skill in this project and build the blog detail page.Sync schema changes made in the dashboard with pull, and use the generated client.

Placing a Skill doesn't set up an API key or create entries. Prepare the connection with the Quickstart.

Updates and overwrites

If you run the same command again, it compares against the template bundled with the CLI you ran. If the content is the same it changes nothing, and if it differs it replaces the file.

To pick up changes from the source, run it again with an updated CLI. If you want to keep text you added by hand, put it in a separate Skill or in your project's instruction file.

How it differs from MCP

For detailed parameters and limits, check MCP or Markdown. Don't rely on a Skill alone to decide the full spec. What an API key can fetch follows the APIs set on that key. See Manage API keys for the settings.