only-in-vsc

Validate repository-level skills for CLI discoverability and frontmatter requirements.

3|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/theomonfort/theomonfort --skill only-in-vsc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: only-in-vsc
Source: https://github.com/theomonfort/theomonfort/tree/main/.github/skills/only-in-vsc
Command: npx skills add https://github.com/theomonfort/theomonfort --skill only-in-vsc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dummy skill used to verify that repository-level skills are detectable by the CLI and properly loaded from .github/skills/.

Core Features & Use Cases

  • Validate that a repo-scoped skill is present and discoverable by the CLI.
  • Serve as a placeholder to ensure proper parsing, loading, and integration of skills in tooling.
  • Use case: CI or local development can confirm the skill is listed among available skills.

Quick Start

Ask the AI to verify that the skill "only-in-vsc" is loadable from the repository and visible to the skill discovery process.

Frequently Asked Questions about only-in-vsc

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

FAQPage Schema
How do I validate that repository-level skills are discoverable by the CLI?

To validate repository-level skills, ensure a SKILL.md entrypoint is present under .github/skills so the CLI can locate and load it. This confirms the skill satisfies frontmatter requirements and is properly listed during discovery.

What is a SKILL.md entrypoint and when do I need it for CLI skill discovery?

A SKILL.md entrypoint is the required file format for repository-level skills to be parsed and loaded by the CLI. You need it during development and CI workflows to verify that skills under .github/skills are discoverable.

How do I check if my .github/skills directory passes frontmatter requirements in CI?

You can check frontmatter requirements by validating that the SKILL.md file includes the required name and description fields. This ensures the CI workflow properly parses the metadata and lists the skill without errors.

Does CLI skill discovery report missing metadata or toxicity risks in repository skills?

Yes, CLI skill discovery reports any missing metadata or toxicity risks found during validation. It checks for the presence of optional components directories and confirms that all required frontmatter fields are satisfied.

Why does my repository skill not show up in the CLI skill discovery list?

Your repository skill may not show up because the SKILL.md entrypoint is missing or lacks required frontmatter like name and description. Validate the file location under .github/skills to ensure it is loadable.

Can I use a dummy skill to test CLI skill loading and parsing in local development?

Yes, you can use a dummy skill to test CLI skill loading and parsing in local development. It serves as a placeholder to verify proper integration, confirm the skill is listed, and ensure the tooling detects repository-scoped skills.