菜单
Locate Rust crate source and documentation paths by asking Cargo instead of assuming ~/.cargo. Use when the user asks to inspect a crate implementation, find local crate files, or get the matching docs.rs URL for a dependency.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Edit or review pvf developer docs under docs/. Use when changing docs/ files, trimming or migrating stale docs, deciding whether information belongs in docs, code comments, or tests, or checking architecture/reference/testing doc ownership and drift risk.
Add, update, place, or review pvf tests and validation. Use when writing regression tests, protecting behavior changes, choosing unit/module/integration test boundaries, reviewing test quality, changing test policy, or deciding validation commands.
Add, edit, rename, or review pvf palette behavior. Use when changing PaletteKind, PaletteProvider implementations, palette open options, provider snapshots, candidate rows, command-palette visibility, input modes, selection behavior, tab or submit behavior, palette-scoped key behavior, or palette rendering contracts.
Add, edit, rename, or review pvf command behavior. Use when changing command ids, arguments, parsing, roles, exposure, invocation policy, target requirements, enabled_when runtime conditions, command palette visibility, key bindings, help text, or command dispatch.
Run and interpret pvf headless performance diagnostics. Use for generating benchmark PDF fixtures, running `cargo bench --bench perf`, writing JSON reports, comparing results across PDFs or code changes, and explaining scenario metrics or regressions.
Add, edit, rename, or review pvf extension behavior. Use when changing Extension implementations, ExtensionHost composition, extension-owned state, input hooks, AppEvent handling, background drain, status bar segments, extension UI snapshots, or reload/reset behavior.
| name | rust-crate-path-locator |
| description | Locate Rust crate source and documentation paths by asking Cargo instead of assuming ~/.cargo. Use when the user asks to inspect a crate implementation, find local crate files, or get the matching docs.rs URL for a dependency. |
Do not assume crates live under ~/.cargo. Use Cargo's resolved metadata first.
cargo metadata --format-version 1.name matches the crate.manifest_path; its directory is the crate source root.https://docs.rs/<crate>/<version>.cargo metadata --format-version 1
If jq is available, this is a convenient filter:
cargo metadata --format-version 1 |
jq -r '.packages[] | select(.name == "ratatui") | "\(.manifest_path)\nhttps://docs.rs/\(.name)/\(.version)"'
If the crate is not in the current dependency graph, say so. For a crate that should be local but has not been fetched yet, run cargo fetch in a project that depends on it, then retry cargo metadata.