configure-docs

Resolve the documentation directory for the active workspace via workspace-docs.json.

1|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill configure-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: configure-docs
Source: https://github.com/bhanford9/vs-code-copilot-tools/tree/main/skills/configure-docs
Command: npx skills add https://github.com/bhanford9/vs-code-copilot-tools --skill configure-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve the documentation directory for the active workspace by consulting a machine-local configuration file, enabling automated discovery and setup of project knowledge bases.

Core Features & Use Cases

  • Workspace docs lookup via workspace-docs.json to locate the docs directory for the current workspace.
  • First-time setup, opt-out toggling, and per-workspace configuration management.
  • Path normalization (lowercase, forward slashes) to ensure cross-machine consistency.
  • Use Case: When agents need to locate or configure the knowledge base directory for the active workspace, or when documentation configuration needs adjustment.

Quick Start

Invoke the configure-docs skill to locate or set the workspace documentation directory for the current project.

Frequently Asked Questions about configure-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically locate the documentation directory for my current workspace?

Workspace docs lookup consults a machine-local JSON configuration file to automatically discover and resolve the documentation directory for the active workspace. It enables automated project knowledge base discovery without manual path entry.

How do I configure workspace documentation paths for first-time project setup?

Configure workspace documentation paths through a machine-local JSON workflow that handles first-time setup, path normalization, and opt-out toggling for unconfigured workspaces. It prompts you to establish the directory during initial invocation.

Does path normalization ensure cross-machine consistency for workspace docs configuration?

Path normalization ensures cross-machine consistency by converting directory paths to lowercase with forward slashes. This standardization allows the machine-local configuration file to maintain uniform workspace docs locations across different operating systems.

Can I opt out of workspace documentation directory configuration?

You can opt out of workspace documentation configuration using the opt-out toggling mechanism built into the JSON workflow. It handles opt-out requests directly within the machine-local configuration file for the active workspace.

When do I need to resolve a documentation directory for an active workspace?

Resolve the documentation directory when any agent or skill needs to locate the knowledge base directory for the active workspace, or when documentation configuration must be checked, changed, or established for project automation.

What happens if a workspace has no documentation configuration set up?

Unconfigured workspaces trigger a prompt during the workspace docs lookup process to establish the documentation directory. The JSON workflow detects the missing configuration and guides first-time setup for the active workspace.