skill-lookup

Name: skill-lookup
Author: f

AI Community

Repo stars 162,706
Author repo prompts.chat

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: > search_skills({"query": "code review", "limit": 5, "category": "coding"}) get_skill({"id": "abc123"}) Use these prompts.chat M…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Workflow”, “Example”, “Available Tools”, “How to Search for Skills”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-lookup directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Workflow / Example / Available Tools” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Workflow

Search for skills matching the user's request using search_skills
Present results with title, description, author, and file list
If the user picks a skill, retrieve it with get_skill to get all files
Install by saving files to .claude/skills/{slug}/ and verify the SKILL.md exists
Confirm installation and explain what the skill does and when it activates

Example

search_skills({"query": "code review", "limit": 5, "category": "coding"})
get_skill({"id": "abc123"})

Available Tools

Use these prompts.chat MCP tools:

search_skills - Search for skills by keyword
get_skill - Get a specific skill by ID with all its files

How to Search for Skills

Call search_skills with:

query: The search keywords from the user's request
limit: Number of results (default 10, max 50)
category: Filter by category slug (e.g., "coding", "automation")
tag: Filter by tag slug

Present results showing:

Title and description
Author name
File list (SKILL.md, reference docs, scripts)
Category and tags
Link to the skill

How to Get a Skill

Call get_skill with:

id: The skill ID

Returns the skill metadata and all file contents:

SKILL.md (main instructions)
Reference documentation
Helper scripts
Configuration files

How to Install a Skill

When the user asks to install a skill:

Call get_skill to retrieve all files
Create the directory .claude/skills/{slug}/
Save each file to the appropriate location:
- SKILL.md → .claude/skills/{slug}/SKILL.md
- Other files → .claude/skills/{slug}/{filename}
Read back SKILL.md to verify the frontmatter is intact

Guidelines

Always search before suggesting the user create their own skill
Present search results in a readable format with file counts
When installing, confirm the skill was saved successfully
Explain what the skill does and when it activates

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: AI
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @f · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Write / modify
Detected network behavior: Local-only
Install commands: None (reference only)

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-lookup.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

## Workflow

1. Search for skills matching the user's request using `search_skills`
2. Present results with title, description, author, and file list
3. If the user picks a skill, retrieve it with `get_skill` to get all files
4. Install by saving files to `.claude/skills/{slug}/` and verify the SKILL.md exists
5. Confirm installation and explain what the skill does and when it activates

## Example

```
search_skills({"query": "code review", "limit": 5, "category": "coding"})
get_skill({"id": "abc123"})
```

## Available Tools

Use these prompts.chat MCP tools:

- `search_skills` - Search for skills by keyword
- `get_skill` - Get a specific skill by ID with all its files

## How to Search for Skills

Call `search_skills` with:

- `query`: The search keywords from the user's request
- `limit`: Number of results (default 10, max 50)
- `category`: Filter by category slug (e.g., "coding", "automation")
- `tag`: Filter by tag slug

Present results showing:
- Title and description
- Author name
- File list (SKILL.md, reference docs, scripts)
- Category and tags
- Link to the skill

## How to Get a Skill

Call `get_skill` with:

- `id`: The skill ID

Returns the skill metadata and all file contents:
- SKILL.md (main instructions)
- Reference documentation
- Helper scripts
- Configuration files

## How to Install a Skill

When the user asks to install a skill:

1. Call `get_skill` to retrieve all files
2. Create the directory `.claude/skills/{slug}/`
3. Save each file to the appropriate location:
   - `SKILL.md` → `.claude/skills/{slug}/SKILL.md`
   - Other files → `.claude/skills/{slug}/{filename}`
4. Read back `SKILL.md` to verify the frontmatter is intact

## Guidelines

- Always search before suggesting the user create their own skill

…

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Workflow → Example → Available Tools → How to Search for Skills → How to Get a Skill → How to Install a Skill
terms    -> 1. Search for skills matching the user's request using searchskills 2. · 1. Call getskill to retrieve all files 2.
files/cmd -> searchskills · getskill · .claude/skills/{slug}/ · query · limit · category · tag · .claude/skills/{slug}/SKILL.md
body sha256 -> 562f4f3dc6e5