Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [Feature Request] Skills management improvements: mobile app registration, API key for sync, per-user usage limits [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#49007•Fetched 2026-04-17 08:53:26
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
ha-uchidaha-uchida
Participants
ha-uchidaha-uchida
Timeline (top)
labeled ×2

Several improvements requested for skills management and organization-level controls in claude.ai.

Root Cause

Several improvements requested for skills management and organization-level controls in claude.ai.

RAW_BUFFERClick to expand / collapse

Summary

Several improvements requested for skills management and organization-level controls in claude.ai.

Requested Improvements

1. Register skills from mobile app

Currently, skills can only be registered from the desktop/web interface. We'd like to be able to register and manage skills from the Claude mobile app as well. This is especially useful when you discover a need while working on mobile.

2. Dedicated API key for skills sync from Claude Code CLI

We'd like to be able to:

  • Issue a dedicated API key from the claude.ai admin panel (separate from the main API key)
  • Use this key to automatically sync/install skills from a local Claude Code setup to claude.ai
  • This API key should be read-only for skills and settings (no API billing access)

Alternatively, allow overwriting/managing skills directly from the Claude chat interface.

3. Per-user usage limit settings

When an organization admin sets a spending limit (e.g., $100), individual users should be able to set their own lower limit (e.g., $50) to self-regulate usage. This helps users be mindful of costs without needing admin intervention.

4. Codebase-aware responses for feature specification checks

When users ask about existing feature specifications or behavior, Claude should actively reference and reason from the connected codebase rather than giving generic responses. This is critical for development workflows where understanding current implementation details matters.

Environment

  • claude.ai with team/organization plan
  • Claude Code CLI users wanting tighter integration with claude.ai

extent analysis

TL;DR

To address the requested improvements for skills management and organization-level controls in claude.ai, focus on enhancing the mobile app, introducing a dedicated API key for skills sync, and implementing per-user usage limit settings.

Guidance

  • Mobile App Enhancement: Develop and integrate a feature to register and manage skills directly from the Claude mobile app to improve user experience and accessibility.
  • Dedicated API Key: Design and implement a separate, read-only API key for skills and settings that can be issued from the claude.ai admin panel and used for syncing skills from the Claude Code CLI.
  • Per-User Limits: Introduce a feature that allows individual users to set their own usage limits, which should be lower than or equal to the organization's set limit, to encourage self-regulation and cost awareness.
  • Codebase Integration: Enhance Claude's response mechanism to reference and reason from the connected codebase when users inquire about feature specifications or behavior, improving its usefulness in development workflows.

Example

No specific code example can be provided without more technical details, but the development should focus on integrating these features into the existing claude.ai and Claude Code CLI infrastructure.

Notes

The implementation details and technical specifications for these improvements are not provided in the issue, so the guidance is based on the functional requirements outlined. The actual development process may vary depending on the existing architecture and technology stack of claude.ai and the Claude Code CLI.

Recommendation

Apply workaround by prioritizing the development of the dedicated API key for skills sync and per-user usage limit settings, as these seem to be critical for immediate user needs and can potentially be developed and deployed independently of the other requested features.

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…
#api#environment variable#network issue#logging issue#authentication issue

Still need to ship something?

×6

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

Back to top recommendations

TRENDING