MCP Scaffolder

Name and description (scaffolding a TypeScript MCP server) align with the SKILL.md: it only describes generating project files, package.json with @modelcontextprotocol/sdk, transport config snippets, and README. No unrelated binaries, services, or credentials are requested.

Instructions stay within scaffolding scope (generate files, tool definitions, config snippets). Two items to note: (1) the stdio config example uses an absolute path for the build artifact — agents producing scaffolds should avoid embedding real absolute paths without user confirmation; (2) the skill tells the agent how to choose transport (stdio vs HTTP) and mentions local file-system/CLI usage for stdio, which is appropriate for scaffolding but could lead to generated code that expects filesystem access when run. The SKILL.md does not instruct the agent to read user's files, env vars, or other system state.

Instruction-only skill with no install spec and no code files — nothing will be downloaded or written by an installer. This is the lowest-risk install model.

The skill declares no required environment variables or credentials. It does instruct generating a .env.example documenting env vars for the scaffolded project, which is expected and proportionate; it does not request or access any secrets itself.

always is false and the skill is user-invocable with normal autonomous invocation behavior. It does not request permanent presence, nor does it instruct modifying other skills or agent-wide settings.