Your agent asks.You approve.rsk installs.

• all
• global
• docs
• design
• go-grpc
• gin
• nethttp
• go-cli
• fastapi
• llm-app
• ros2
• python-grpc
• python-cli
• event-driven
• observability
• code-review
• --include personal

Showing the 51 skills rsk catalog lists by default; the 9 personal ones need --include personal.

From internal/mcp/tools.go

Three tools. One writes, and it is marked to say so.

The descriptions are the ones the agent reads. destructiveHint is only advice to the client; the requiresUserInteraction flag is what makes Claude Code prompt you even in auto-approve modes.

• project_profile

  Detect this project's stack from its files and propose the ralvaskills skills that apply. Call it before scaffolding or a non-trivial change.

  readOnlyHint: true
  destructiveHint: false
  idempotentHint: true

• search_skills

  Search the ralvaskills catalog by keyword. Use it to find a skill by name or intent when project_profile does not name one.

  readOnlyHint: true
  destructiveHint: false
  idempotentHint: true

• install_skills

  Install one or more skills or bundles into this project by name, resolving them through the ralvaskills catalog. Writes symlinks and the project manifest. The client asks the user to approve.

  readOnlyHint: false
  destructiveHint: true
  _meta: anthropic/
    requiresUserInteraction

• rsk://catalog

  A resource, not a tool: every skill with its latest version, descriptions cut to 200 characters. Name rsk-catalog.

  mimeType:
    application/json

From internal/mcp/signals.go

What project_profile looks for.

{
 "candidates": [
  {
   "because": [
    "language:go"
   ],
   "installed": false,
   "latest": "1.14.0",
   "skill": "go-architect"
  },
  {
   "because": [
    "infra:docker"
   ],
   "installed": false,
   "latest": "1.3.0",
   "skill": "docker-architect"
  },
  {
   "because": [
    "repo:cli"
   ],
   "installed": false,
   "latest": "1.0.0",
   "skill": "cli-tool-architect"
  }
 ],
 "installed": [],
 "manifest": {
  "exists": false,
  "pinned": 0,
  "skills": 0
 },
 "project_root": "/tmp/rsk-demo-go",
 "signals": [
  {
   "kind": "language:go",
   "proof": "go.mod"
  },
  {
   "kind": "infra:docker",
   "proof": "Dockerfile"
  },
  {
   "kind": "repo:cli",
   "proof": "cmd/demo/main.go"
  }
 ]
}

The whole surface

Thirteen commands, grouped the way rsk --help groups them.

• Machine setup

  init

  Set up rsk for this machine.

• Project lifecycle

  new

  Initialize an rsk project in the current directory.

  destroy

  Remove the rsk project from the current directory.

• Install / uninstall / update

  install

  Install bundles or skills.

  uninstall

  Remove installed bundles or skills.

  update

  Pull the latest skills and re-link.

• Project pinning

  pin

  Pin a skill so it is imported into each tool's project config.

• Tool configuration

  tools

  Manage tool permissions (allow/deny/list/remove).

• Read-only views

  catalog

  Browse the catalog of available skills and bundles.

  list

  Show installed skills (project / --global).

  status

  Show installed skills and version drift.

• Other

  mcp

  Run the MCP server over stdio.

  completion

  Generate the autocompletion script for the specified shell.

Data on stdout, logs on stderr, --output json on the read-only views, NO_COLOR honoured.

The trade-off

One binary and one config file for every project. One dependency in exchange.

Questions

Before you install.