AI & agents · Learning & explanation
guide
/guide
Ask about rp1 capabilities, discover skills, and get workflow guidance.
Assessment and security
96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability21 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
Deprecation
No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.
Licence
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Ask about rp1 capabilities, discover skills, and get workflow guidance.
Original author description
Ask about rp1 capabilities, discover skills, and get workflow guidance.
How it works
- Companion Docs
- 1. No-Question Mode (Capability Overview)
- 2. Intent Classification
- 3. Answer Routing
- 4. Dynamic Validation
- 5. Suggestion Format
- 6. Invocation
- 7. Response Style
Original SKILL.md headings · 120 lines, 895 words
SKILL.md preview
---
name: guide
description: "Ask about rp1 capabilities, discover skills, and get workflow guidance."
allowed-tools: Bash(echo *), Bash(rp1 *)
metadata:
category: knowledge
is_workflow: false
version: 1.0.0
tags:
- core
- discovery
- documentation
created: 2026-04-06
author: cloud-on-prem/rp1
arguments:
- name: QUESTION
type: string
required: false
description: "What you want to know about rp1 (omit for capability overview)"
---
# /guide - rp1 Capability Guide
You help users discover, understand, and invoke rp1 skills. You answer questions about what rp1 can do, recommend the right skill for a task, explain workflow sequences, and offer to run skills on the user's behalf.
## Companion Docs
Two reference files sit alongside this skill. Load them based on intent (see routing below):
- **CATALOG.md** -- Full skill catalog organized by category. Use for discovery, comparison, and "what can rp1 do?" questions.
- **WORKFLOWS.md** -- Multi-skill composition patterns. Use for workflow, sequencing, and "how do I do X end-to-end?" questions.
## 1. No-Question Mode (Capability Overview)
If QUESTION is empty or omitted, provide a concise capability overview:
1. Read `CATALOG.md` (companion doc, same directory as this skill).
2. Run `rp1 list --json` to get installed skills.
3. Present a summary organized by category showing only skills installed on `CURRENT_HOST`:
- Category name and when to use it
- Skill names with one-line descriptions
- Highlight workflow skills (marked in catalog)
4. End with: "Ask me anything about these skills, or tell me what you're trying to do and I'll recommend the right one."
## 2. Intent Classification
When QUESTION is provided, classify it into exactly one category:
| Intent | Signal | Source |
|--------|--------|--------|
| **discovery** | "What skills...", "list...", "show me...", "what can rp1 do" | CATALOG.md |
| **comparison** | "Difference between...", "X vs Y", "which should I use", "when to use X over Y" | CATALOG.md |
| **workflow** | "How do I do X end-to-end", "what order", "after X what's next", "workflow for..." | WORKFLOWS.md |
| **how-to** | "How do I use X", "how to run", "what flags", "parameters for..." | WORKFLOWS.md, then CATALOG.md |
| **troubleshooting** | "X isn't working", "error with", "why does X fail", "can't find skill" | `docs/reference/` files |
| **meta** | "How does rp1 work internally", "architecture of", "how is X built" | `docs/reference/` files |
Classification rules:
- Match the strongest signal. When ambiguous, prefer the category whose source is lighter (discovery > workflow > troubleshooting).
- A question can touch multiple categories. Pick the primary intent and note secondary sources to consult if the primary answer is insufficient.
## 3. Answer Routing
### 3.1 Fast Path (discovery, comparison)
1. Read `CATALOG.md` (companion doc).
2. Answer directly from catalog content. No other tool calls needed.
3. For comparison queries, pull relevant entries and contrast them side-by-side (purpose, scope, workflow indicator, key arguments).
### 3.2 Fast Path (workflow, how-to)
1. Read `WORKFLOWS.md` (companion doc).
2. For workflow queries, find the matching composition pattern and present the sequence with chaining explanation.
3. For how-to queries, check WORKFLOWS.md first for multi-step guidance, then fall back to CATALOG.md for single-skill parameter details.
### 3.3 Deep Path (troubleshooting, meta)
1. Read the relevant file(s) from `docs/reference/`:
- Skill-specific: `docs/reference/{plugin}/{skill-name}.md` (plugin is `base`, `dev`, or `cli`)
- Plugin overview: `docs/reference/{plugin}/index.md`
- General reference: `docs/reference/index.md`
2. If the question is about CLI behavior, also check `docs/reference/cli/`.
3. Synthesize an answer from the reference content.
## 4. Dynamic Validation
Before presenting any skill recommendation, validate it is installed for `CURRENT_HOST`.
```
rp1 list --json
```
Parse the JSON array. Each entry includes:
- `name`: Platform-neutral skill name (for example `guide`)
- `description`
- `plugin`: Plugin id (`base`, `dev`, or `utils`)
- `canonical_name`: Canonical skill id (`base:guide`)
- `user_facing_name`: Canonical user-facing name (`rp1-base:guide`)
- `installed_platforms`: Hosts where this skill is installed (`claude-code`, `opencode`, `codex`, `copilot`, `antigravity`)
- `invocations`: Host-specific invocation strings for installed hosts
`CURRENT_HOST` is injected into this built skill by the build pipeline and will be one of the supported platform ids such as `claude-code`, `opencode`, `codex`, `copilot`, or `antigravity`. Use `CURRENT_HOST` directly when filtering and presenting skills:
- Only recommend skills whose `installed_platforms` includes `CURRENT_HOST`.
- Use `invocations[CURRENT_HOST]` when presenting or invoking a skill.
- If a skill exists in `CATALOG.md` or `WORKFLOWS.md` but is not installed on `CURRENT_HOST`, mark it unavailable here and suggest `rp1 install {CURRENT_HOST}` instead of plugin-based remediation.
Run this validation once per invocation. Cache the result for the duration of the response.
## 5. Suggestion Format
When recommending a skill, use this format for each suggestion:
**`<host-specific invocation>`** -- One sentence explaining why this skill fits the user's situation.
> Want me to run it? I can invoke `<host-specific invocation>` with [inferred parameters, if any].
Rules:
- Use `invocations[CURRENT_HOST]`.
- One sentence of relevance, grounded in what the user asked or described.
- Offer to invoke. Pre-fill parameters you can infer from context (e.g., a feature ID mentioned in the conversation, a file path, a branch name).
- Wait for user confirmation before invoking. Never auto-invoke.
- Limit to 3 suggestions maximum per response. Rank by relevance.
## 6. Invocation
When the user accepts an invocation offer:
1. Confirm the parameters you will use.
2. Invoke the skill using `invocations[CURRENT_HOST]`, or tell the user the exact command to run.
3. Do not invoke skills the user has not confirmed.
## 7. Response Style
- Be direct and concise. Lead with the answer, not preamble.
- Use tables for comparisons. Use bullet lists for enumerations.
- Quote skill names with `/` prefix consistently.
- When a question has a definitive answer, give it. When it depends on context, present the decision factors.
- Do not repeat the full catalog unless specifically asked. Surface only the relevant subset.
Files in this package (3)
- CATALOG.md 8 KB
- SKILL.md 6 KB
- WORKFLOWS.md 14 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · rp1-run/rp1 | 96 | Apache-2.0 |
| YuDefine/nuxt-supabase-starter | 100 | MIT |
| toss/es-toolkit | 100 | MIT |
| vecten/vecten-open | 100 | Apache-2.0 |
| MassimilianoBiancucci/find_home | 100 | Apache-2.0 |
| testany-io/testany-agent-skills | 100 | MIT |
| rlibre/x4 | 100 | MIT |
| CoeusInstitute/hermes-ide | 100 | MIT |
| voyager67/Claude-Garage | 100 | MIT |
Database snapshot: 13.11.2026 · package version e69af8d4355c (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist… - 95skills-authoring
Guide to writing SKILL.md files for Claude Code. Use when creating skills that provide on-demand reference, methodology, or workflow guidance. - 100find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist… - 100find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist… - 100find-skills
Discover and install reusable agent skills when users ask for capabilities, workflows, or domain-specific help that may already exist as an installable skill. - 100find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist…