Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Feature]: Add install verification step and Windows guidance to the agent skills install docs

Aperta
  • Qualcosa non va?
#113 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@croblesm ci sta già lavorando.

Dal 16/7/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement internal-user
Use case

A developer on Windows follows the site's primary install path (npx skills add) to use the agent skills with Claude Code, Codex, or Cursor. The installer reports success, but the skills never load in the agent (see bug #[X]). Because the failure is silent, the developer's next observation is an unskilled agent defaulting to SQLite/Postgres/the mssql/server image, and the natural conclusion is "the skills don't work," which reads as a product failure rather than an install failure.

Current workaround

Manually copying the skill folders into the agent's documented skills directory (e.g. .claude/skills for Claude Code), per the README's manual install method. Verified working: all 10 skills load and trigger as designed after the copy.

Proposed behavior
  1. A one-line verification step at the end of the install instructions: start the agent and ask "what skills do you have available," and confirm the azuresql-db skills appear. Catches silent install failures immediately.
  2. A Windows note documenting the manual copy as the reliable path until the CLI's Windows install (symlink step) is validated.
Who benefits

All developers

Urgency

Important for my Public Preview adoption

Additional context

Related: bug #[X] (root cause: skills installed to .agents/skills, agent-specific link not created on Windows). Only Claude Code verified; other agents likely affected the same way.

Lingua principale
Shell
Stelle
19
Fork
6
Merge medio
7h 24m
PR unite (30g)
3

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di microsoft/azure-sql-database-container

Tutte le issue di microsoft/azure-sql-database-container

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.