find-skills

Name: find-skills
Author: kanyun-inc

57stars3forks

How to install find-skills?

kanyun-inc/reskill/find-skills

$npx -y skills add kanyun-inc/reskill --skill find-skills

Installs into the current project.

Summary

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. Uses reskill as the package manager.

Files · 1

View on GitHub

SKILL.md

1	# Find Skills (reskill)
2
3	This skill helps you discover and install skills from the reskill ecosystem.
4
5	> Key Principles:
6	> 1. Search → Present → Ask → Install — always show results first, ask the user before installing.
7	> 2. Be registry-aware — check if the project has a configured registry (private or public) and tell the user which registry you're searching. If results are empty, suggest the user may need to configure a private registry.
8
9	## When to Use This Skill
10
11	Use this skill when the user:
12
13	- Asks "how do I do X" where X might be a common task with an existing skill
14	- Says "find a skill for X" or "is there a skill for X"
15	- Asks "can you do X" where X is a specialized capability
16	- Expresses interest in extending agent capabilities
17	- Wants to search for tools, templates, or workflows
18	- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
19
20	## What is reskill?
21
22	reskill is a Git-based package manager for AI agent skills. It provides declarative configuration, version locking, and seamless synchronization for managing skills across projects and teams.
23
24	CLI usage:
25
26	If `reskill` is installed globally, use it directly. Otherwise use `npx reskill@latest`:
27
28	```bash
29	# Global install
30	reskill <command>
31
32	# Or via npx (no install needed)
33	npx reskill@latest <command>
34	```
35
36	Registry configuration:
37
38	The `find` command automatically resolves the registry in this order:
39
40	1. `--registry <url>` CLI option (highest priority)
41	2. `RESKILL_REGISTRY` environment variable
42	3. `defaults.publishRegistry` in `skills.json`
43	4. Public registry `https://reskill.info/` (fallback)
44
45	To configure a custom registry for the project, add it to `skills.json`:
46
47	```json
48	{
49	"defaults": {
50	"publishRegistry": "https://your-registry.example.com/"
51	}
52	}
53	```
54
55	Once configured, all `find` / `install` commands will use it automatically — no need to pass `--registry` every time.
56
57	Key commands for skill discovery:
58
59	- `reskill find <query>` — Search for skills by keyword
60	- `reskill find <query> --json` — Search with machine-readable JSON output
61	- `reskill install <ref>` — Install a skill
62	- `reskill list` — List installed skills
63	- `reskill info <skill>` — Show skill details
64
65	## How to Help Users Find Skills
66
67	### Step 0: Check Registry Context
68
69	Before searching, determine which registry to use (see "Registry configuration" above for the full priority order).
70
71	Check these sources:
72	1. `RESKILL_REGISTRY` environment variable
73	2. `defaults.publishRegistry` in `skills.json`
74
75	If either is configured → use it, and tell the user which registry you're searching.
76
77	If neither is configured → ask the user before proceeding:
78
79	```
80	No private registry is configured for this project.
81
82	Do you want to search a private registry? If so, provide the URL
83	(e.g. --registry https://your-registry.example.com/).
84
85	Otherwise, I'll search the public registry (reskill.info).
86	```
87
88	Once the user responds:
89	- User provides a URL → use it with `--registry <url>`
90	- User says no / skip → proceed with the public registry (`https://reskill.info/`)
91
92	### Step 1: Understand What They Need
93
94	When a user asks for help with something, identify:
95
96	1. The domain (e.g., React, testing, design, deployment)
97	2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
98	3. Whether this is a common enough task that a skill likely exists
99
100	### Step 2: Search for Skills (Progressive Strategy)
101
102	Use `--json` for structured results:
103
104	```bash
105	npx reskill@latest find "<query>" --json
106	```
107
108	The JSON output has this structure:
109
110	```json
111	{
112	"total": 2,
113	"items": [
114	{
115	"name": "@scope/skill-name",
116	"description": "What this skill does",
117	"latest_version": "1.0.0",
118	"keywords": ["keyword1", "keyword2"],
119	"publisher": { "handle": "author" },
120	"updated_at": "2025-01-01T00:00:00Z"
121	}
122	]
123	}
124	```
125
126	IMPORTANT: Use progressive search to maximize results. The registry may not support multi-word fuzzy matching, so follow this strategy:
127
128	#### Round 1: Try the natural query first
129
130	```bash
131	npx reskill@latest find "frontend design" --json
132	```
133
134	If `total > 0`, proceed to Step 3 (present results).
135
136	#### Round 2: Try hyphenated version
137
138	Skill names often use hyphens. If Round 1 returns 0 results, try connecting keywords with a hyphen:
139
140	```bash
141	npx reskill@latest find "frontend-design" --json
142	```
143
144	#### Round 3: Broaden to the most relevant single keyword
145
146	If still 0 results, pick the most specific keyword from the user's query and search with that alone:
147
148	```bash
149	npx reskill@latest find "frontend" --json
150	```
151
152	Choose the keyword that best narrows the domai

People who liked this also viewed

6 picks

Type

find-skills

57stars3forks

View on GitHub

How to install find-skills?

kanyun-inc/reskill/find-skills

$npx -y skills add kanyun-inc/reskill --skill find-skills

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Find Skills (reskill)
2
3	This skill helps you discover and install skills from the reskill ecosystem.
4
5	> Key Principles:
6	> 1. Search → Present → Ask → Install — always show results first, ask the user before installing.
7	> 2. Be registry-aware — check if the project has a configured registry (private or public) and tell the user which registry you're searching. If results are empty, suggest the user may need to configure a private registry.
8
9	## When to Use This Skill
10
11	Use this skill when the user:
12
13	- Asks "how do I do X" where X might be a common task with an existing skill
14	- Says "find a skill for X" or "is there a skill for X"
15	- Asks "can you do X" where X is a specialized capability
16	- Expresses interest in extending agent capabilities
17	- Wants to search for tools, templates, or workflows
18	- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
19
20	## What is reskill?
21
22	reskill is a Git-based package manager for AI agent skills. It provides declarative configuration, version locking, and seamless synchronization for managing skills across projects and teams.
23
24	CLI usage:
25
26	If `reskill` is installed globally, use it directly. Otherwise use `npx reskill@latest`:
27
28	```bash
29	# Global install
30	reskill <command>
31
32	# Or via npx (no install needed)
33	npx reskill@latest <command>
34	```
35
36	Registry configuration:
37
38	The `find` command automatically resolves the registry in this order:
39
40	1. `--registry <url>` CLI option (highest priority)
41	2. `RESKILL_REGISTRY` environment variable
42	3. `defaults.publishRegistry` in `skills.json`
43	4. Public registry `https://reskill.info/` (fallback)
44
45	To configure a custom registry for the project, add it to `skills.json`:
46
47	```json
48	{
49	"defaults": {
50	"publishRegistry": "https://your-registry.example.com/"
51	}
52	}
53	```
54
55	Once configured, all `find` / `install` commands will use it automatically — no need to pass `--registry` every time.
56
57	Key commands for skill discovery:
58
59	- `reskill find <query>` — Search for skills by keyword
60	- `reskill find <query> --json` — Search with machine-readable JSON output
61	- `reskill install <ref>` — Install a skill
62	- `reskill list` — List installed skills
63	- `reskill info <skill>` — Show skill details
64
65	## How to Help Users Find Skills
66
67	### Step 0: Check Registry Context
68
69	Before searching, determine which registry to use (see "Registry configuration" above for the full priority order).
70
71	Check these sources:
72	1. `RESKILL_REGISTRY` environment variable
73	2. `defaults.publishRegistry` in `skills.json`
74
75	If either is configured → use it, and tell the user which registry you're searching.
76
77	If neither is configured → ask the user before proceeding:
78
79	```
80	No private registry is configured for this project.
81
82	Do you want to search a private registry? If so, provide the URL
83	(e.g. --registry https://your-registry.example.com/).
84
85	Otherwise, I'll search the public registry (reskill.info).
86	```
87
88	Once the user responds:
89	- User provides a URL → use it with `--registry <url>`
90	- User says no / skip → proceed with the public registry (`https://reskill.info/`)
91
92	### Step 1: Understand What They Need
93
94	When a user asks for help with something, identify:
95
96	1. The domain (e.g., React, testing, design, deployment)
97	2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
98	3. Whether this is a common enough task that a skill likely exists
99
100	### Step 2: Search for Skills (Progressive Strategy)
101
102	Use `--json` for structured results:
103
104	```bash
105	npx reskill@latest find "<query>" --json
106	```
107
108	The JSON output has this structure:
109
110	```json
111	{
112	"total": 2,
113	"items": [
114	{
115	"name": "@scope/skill-name",
116	"description": "What this skill does",
117	"latest_version": "1.0.0",
118	"keywords": ["keyword1", "keyword2"],
119	"publisher": { "handle": "author" },
120	"updated_at": "2025-01-01T00:00:00Z"
121	}
122	]
123	}
124	```
125
126	IMPORTANT: Use progressive search to maximize results. The registry may not support multi-word fuzzy matching, so follow this strategy:
127
128	#### Round 1: Try the natural query first
129
130	```bash
131	npx reskill@latest find "frontend design" --json
132	```
133
134	If `total > 0`, proceed to Step 3 (present results).
135
136	#### Round 2: Try hyphenated version
137
138	Skill names often use hyphens. If Round 1 returns 0 results, try connecting keywords with a hyphen:
139
140	```bash
141	npx reskill@latest find "frontend-design" --json
142	```
143
144	#### Round 3: Broaden to the most relevant single keyword
145
146	If still 0 results, pick the most specific keyword from the user's query and search with that alone:
147
148	```bash
149	npx reskill@latest find "frontend" --json
150	```
151
152	Choose the keyword that best narrows the domai

People who liked this also viewed

6 picks

Type