Context7 Project Bootstrapper
Build a complete VS Code project scaffold using current library documentation.
The skill scopes itself to complete project initialization and says to operate only in an empty folder or after a workspace has been created, which limits accidental impact; however, it lacks user-confirmation requirements, permission boundaries for dependency installation, data-flow disclosure, sensitive-data handling, rollback, and recovery guidance, so points are deducted.
The two-step flow is short and broadly coherent, but the instruction to first call a workspace-creation tool is ambiguous, and there are no diagnosable behaviors for unavailable Context7, failed library resolution, missing documentation, or non-empty directories; the static evidence supports only a conservative score.
Trigger and non-trigger scenarios are relatively explicit and cover several frameworks; however, inputs, output format, capability boundaries, and semantic invocation conditions remain underspecified, with no evidence of Chinese-language support or mainland-China network reachability, so points are deducted.
The name, description, and two-step structure are readable, while the repository README and LICENSE establish MIT licensing, Microsoft attribution, and general maintenance context; the skill itself lacks installation/dependency notes, examples, FAQs, limitation disclosure, versioning, changelog, and explicit maintenance ownership, so points are deducted.
Context7 documentation lookup could provide current library information for setup; however, the skill claims to create folders, dependencies, configuration, and boilerplate while its actual instructions only resolve a library and fetch documentation, with no file-generation, validation, or directly usable output procedure. Substantial user or agent work remains, so points are deducted.
The skill text is auditable, and the repository includes general CI and test materials; nevertheless, the supplied files contain no skill-specific tests, execution results, or third-party reproduction evidence. The unrelated CI files do not validate this skill, so points are deducted.
- Core behavior depends on Context7 tools, but installation, permissions, fallback behavior, and mainland-China reachability are unspecified.
- There is a capability gap between the comprehensive setup claim and instructions that only query documentation; file creation, dependency confirmation, validation, error handling, and rollback should be documented.
- Do not treat repository-wide CI, tests, or Microsoft provenance as evidence that this skill itself was executed or specifically validated.
What it does & when to use it
This skill initializes complete projects in a VS Code workspace rather than creating individual files or changing an existing codebase. It targets scenarios such as TypeScript, React, Node.js, MCP server, VS Code extension, Next.js, and Vite setup. It first uses Context7 tools to resolve library identifiers and retrieve scaffolding guidance, then can establish the project structure, dependencies, configuration, starter code, and development or build instructions. It is intended for an empty folder or a newly created workspace, not for single-file creation, debugging, or repairs.
Given project requirements, it calls mcp_context7_resolve-library-id to resolve library identifiers and then calls mcp_context7_get-library-docs to retrieve scaffolding instructions. It can create a complete folder structure, manage package.json and dependencies, generate configuration such as tsconfig and ESLint files, provide starter boilerplate, and include development, build, and run instructions. It is for full project initialization, not individual file creation, existing-code changes, or debugging.
- A developer wants a new TypeScript project with its folders, dependencies, configuration, and setup guidance.
- A user wants to initialize a React, Next.js, or Vite application rather than add one component file.
- A developer needs a complete Node.js server structure.
- A user wants to initialize an MCP server with a full project layout.
- A developer wants proper scaffolding for a VS Code extension.
- A user explicitly asks to create a new project, create a workspace, or set up a framework project.
Pros & cons
- Covers the full initialization path from directory structure through dependencies, configuration, starter code, and run guidance.
- Clearly separates complete project setup from single-file creation, existing-project changes, and debugging.
- Uses Context7 library, API, and documentation lookups for framework-oriented scaffolding.
- Explicitly covers TypeScript, React, Node.js, MCP servers, VS Code extensions, Next.js, and Vite scenarios.
- It is not intended for adding one file or component to an existing project.
- The target folder must be empty, or workspace creation must happen first.
- The supplied source does not document standalone installation, Context7 service configuration, or failure handling.
- SKILL.md does not provide a test suite or an exhaustive compatibility list for specific frameworks.
How to install
The skill is located at https://github.com/microsoft/vscode under extensions/copilot/assets/prompts/skills/project-setup-info-context7/SKILL.md. The supplied material does not document a standalone installation or registration command. The README states that the overall repository is MIT licensed and includes a Dev Containers / GitHub Codespaces development container. Those repository development instructions should not be treated as a separate installation procedure for this skill.
How to use
Use it in an empty folder or after creating a workspace. Example requests include “Create a new TypeScript project with a complete folder structure, dependencies, configuration, and run instructions” or “Set up a Vite React project.” The documented sequence is to call mcp_context7_resolve-library-id, call mcp_context7_get-library-docs, and then initialize the project from the resulting guidance. Do not use it for “create a file,” “add a component,” existing-code modifications, simple demonstrations, or debugging.