skill-view
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 9 GitHub stars
Code Uyari
- network request — Outbound network request in src/api.ts
- process.env — Environment variable access in src/server/cli.ts
- process.env — Environment variable access in src/server/server.test.ts
- network request — Outbound network request in src/server/server.test.ts
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
Local-only web GUI for inspecting Claude Code skills across user, project, plugin, cache, and marketplace sources
skillview
A local-only web GUI for inspecting Claude Code skills across personal, project, plugin, cache, and marketplace sources.
npx @pc_style/skillview
Run it from the workspace you want to inspect. Skillview opens a browser and builds a provenance-aware inventory from your local Claude configuration.
highlights
- provenance-aware — the same skill can appear as an installed plugin copy, a cached version, and a marketplace source; each record keeps its source, plugin, marketplace, and version context
- fast filtering — search by name, description, or path; filter by source and lifecycle
- deep inspection — rendered Markdown, raw
SKILL.md, file trees, and metadata for every skill - safe by design — read-mostly, localhost-only, no cloud sync
![]() |
![]() |
| instant search across 100+ skills | full provenance: plugin, marketplace, version |
sources
Skillview discovers:
| source | where |
|---|---|
| user | direct skills in ~/.claude/skills/<name>/SKILL.md |
| linked | valid symlinks explicitly exposed inside ~/.claude/skills |
| project | .claude/skills directories beneath the selected workspace |
| installed plugin | active installations recorded in ~/.claude/plugins/installed_plugins.json |
| plugin cache | current, historical, and orphaned skill copies under ~/.claude/plugins/cache |
| marketplace | available plugin skills under registered local marketplace checkouts |
Skillview deliberately does not scan ~/.agents/skills wholesale. A shared skill appears only when it is explicitly linked into ~/.claude/skills. Ephemeral runtime bundles under /private/tmp are also excluded from the standalone package.
options
--workspace <path> workspace to scan instead of the current directory
--port <number> localhost port, or 0 for an available port (default: 4173)
--no-open start the server without opening a browser
-h, --help show help
Examples:
npx @pc_style/skillview --workspace ~/projects/my-app
npx @pc_style/skillview --port 4317 --no-open
SKILL_VIEW_WORKSPACE_ROOT remains available as an environment override.
lifecycle labels
| label | meaning |
|---|---|
enabled / disabled |
direct user/project skill state, or installed plugin state from Claude settings |
installed |
plugin is registered but has no explicit enabled boolean |
cached |
managed plugin cache artifact |
available |
marketplace source that may not be installed |
what it does
- previews skill descriptions, rendered Markdown, raw
SKILL.md, metadata, and file trees - searches and filters by source and lifecycle
- shows plugin, marketplace, version, linked-target, and canonical-path provenance
- copies paths and skill content
- reveals freshly validated skill folders in Finder on macOS
- enables or disables direct user/project skills by renaming
SKILL.mdtoSKILL.md.disabledand back, after confirmation
every skill's file tree, one click away
safety
Skillview binds only to 127.0.0.1. Skill content stays on your machine and is never sent to a cloud service.
All actions use server-issued skill IDs. Before reveal or toggle, the server freshly rediscovers the record, validates its source and canonical path, and checks its capabilities. Raw client-provided filesystem paths are not accepted.
Plugin cache, marketplace, installed-plugin, and linked records are inspection-only. Their files are managed by Claude/plugin tooling and are never renamed by Skillview. Project and marketplace traversal is bounded and does not follow symlinks.
Deletion and arbitrary file editing are deliberately unavailable.
local development
Requires Node.js 20 or newer.
npm install
npm run dev
Build and run the same standalone server shipped in the package:
npm run build
npm start -- --no-open
checks
npm test
npm run build
npm pack --dry-run
The suite covers frontmatter parsing, all six source kinds, linked-skill handling, plugin registry validation, provenance-preserving IDs, action authorization, static asset isolation, and the production HTTP boundary.
publishing
Publishing is intentionally manual:
npm pack --dry-run
npm publish --dry-run
npm publish
license
MIT
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi

