claude-code - 💡(How to fix) Fix [FEATURE] npx-style ephemeral skill execution from remote URL/registry [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46408Fetched 2026-04-11 06:21:05
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Participants
Timeline (top)
labeled ×3

Code Example

claude skill run https://gist.github.com/.../SKILL.md
claude --skill <url-or-package-ref>
RAW_BUFFERClick to expand / collapse

Problem Statement

Currently, skills must be installed as SKILL.md files in ~/.claude/skills/ or .claude/skills/ before they can be used. There's no way to try out or run a skill once without persisting it to the filesystem. For one-off tasks or evaluating community skills, this creates unnecessary friction: install → use → manually delete.

Proposed Solution

An npx-style mechanism to run a skill ephemerally from a remote source (URL, gist, registry) without saving it locally. For example:

claude skill run https://gist.github.com/.../SKILL.md
claude --skill <url-or-package-ref>

The skill would be fetched, loaded for the current session only, and discarded afterward. No files written to disk.

Alternative Solutions

  • Paste skill instructions directly into chat (works but loses structured metadata like allowed-tools, description)
  • Install to filesystem, use, then manually rm -rf the skill directory
  • #46308 proposes path-based invocation for local files, which helps but still requires the file on disk
  • #41068 covers on-demand loading but focuses on performance, not ephemeral usage

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

extent analysis

TL;DR

Implement an npx-style mechanism to run skills ephemerally from a remote source without saving them locally.

Guidance

  • Investigate using a temporary directory to store the fetched skill, allowing it to be loaded and discarded after use without modifying the existing filesystem-based skill installation mechanism.
  • Consider adding a new CLI flag or command to support ephemeral skill execution, such as claude skill run or claude --skill.
  • Evaluate the feasibility of integrating with existing package registries or URL-based repositories to fetch skills, ensuring proper error handling and security measures.
  • Review the proposed solution in the context of related issues, such as #46308 and #41068, to ensure a comprehensive approach to skill execution and loading.

Example

claude skill run https://gist.github.com/.../SKILL.md

This example demonstrates the proposed npx-style mechanism for running a skill ephemerally from a remote source.

Notes

The implementation should prioritize security and ensure that ephemeral skills do not introduce vulnerabilities or persist sensitive data. Additionally, consider the potential impact on performance and existing workflows.

Recommendation

Apply workaround: Implement the proposed npx-style mechanism to provide an interim solution for ephemeral skill execution, allowing users to try out skills without persisting them to the filesystem.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING