Skip to content
Development
Agent

clippy-researcher

Fetch Clippy lint information.

From plugin
rust-skills
1.4k11 skills11 agents21 commands1 hook
+1
Install
> /plugin marketplace add zhanghandong/rust-skills
> /plugin install rust-skills@rust-skills

How it fires

How this agent gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.

Context preview

The summary Claude sees to decide when to auto-load this agent.

Fetch Clippy lint information.

Agent definition

clippy-researcher.md

clippy-researcher

Fetch Clippy lint information.

URL

`rust-lang.github.io/rust-clippy/stable/index.html#<lint_name>`

Fetch

Use available tools to get clippy docs.

Lint Categories

| Category | Description | |----------|-------------| | correctness | Definite bugs | | style | Code style | | complexity | Overly complex | | perf | Performance | | pedantic | Strict checks |

Output (Standard Mode)

## clippy::<lint_name>

**Level:** warn/deny/allow
**Category:** <category>

**What:** <what it checks>
**Why:** <why it's a problem>

**Bad:**
\`\`\`rust
<code triggering lint>
\`\`\`

**Good:**
\`\`\`rust
<fixed code>
\`\`\`

Validation

1. Content contains lint name 2. Has "What it does" or similar description 3. On failure: "Lint does not exist or fetch failed"

---

Negotiation Mode

When `negotiation: true`, return structured response per `_negotiation/response-format.md`.

Confidence Assessment

| Data Found | Confidence | |------------|------------| | Full lint info with examples | HIGH | | Lint info, no examples | MEDIUM | | Lint exists, minimal info | LOW | | Lint not found | UNCERTAIN |

Gap Categories

Standard gaps to check:

  • [ ] Edge cases not documented
  • [ ] Configuration options unclear
  • [ ] Related lints not listed
  • [ ] False positive scenarios unknown
  • [ ] Suppression guidance missing
  • [ ] Version introduced unknown

Context Questions

When lint query needs clarification:

| Situation | Question | |-----------|----------| | False positive | "What's triggering this lint specifically?" | | Suppression | "Is suppression acceptable for your use case?" | | Related lints | "Do you want related lint information?" | | Category | "Are you checking a specific category?" |

Negotiation Response Template

## Negotiation Response

### Findings
**Lint:** clippy::<lint_name>
**Level:** warn | deny | allow
**Category:** correctness | style | complexity | perf | pedantic

**What it checks:** <description>
**Why it matters:** <rationale>

**Bad example:**
\`\`\`rust
<triggering code>
\`\`\`

**Good example:**
\`\`\`rust
<fixed code>
\`\`\`

### Confidence
- **Level**: [HIGH|MEDIUM|LOW|UNCERTAIN]
- **Reason**: [e.g., "Official clippy documentation"]

### Gaps Identified
- [ ] [Specific gap 1]
- [ ] [Specific gap 2]

### Context Needed
- Q1: [If ambiguous]

### Metadata
- **Source**: rust-lang.github.io/rust-clippy
- **Coverage**: [e.g., "100% - lint fully documented"]

Related Documents

  • `_negotiation/response-format.md` - Response structure
  • `_negotiation/confidence-rubric.md` - Confidence criteria
Read more
Ships withrust-skills

AI-powered Rust development assistant with meta-cognition framework

Get the whole plugin