Validate Repo

Validate Foundry-style repositories for structure, required files, links, and secrets.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/beekeeper-lab/foundry --skill validate-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Validate Repo
Source: https://github.com/beekeeper-lab/foundry/tree/main/ai-team-library/claude/skills/validate-repo
Command: npx skills add https://github.com/beekeeper-lab/foundry --skill validate-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runs a comprehensive health check against a generated project or any repo that follows the Foundry structure. This ensures folder expectations, required files, template completeness, broken internal links, and stack-specific tooling, producing a pass/fail checklist with actionable remediation for every finding.

Core Features & Use Cases

  • Validates folder structure and presence of required files (CLAUDE.md, ai/team/composition.yml).
  • Checks for broken internal links and potential secrets exposure.
  • Performs stack-specific validations (lint/test/build commands) and reports remediation guidance.
  • Useful as a pre-export gate before sharing a generated project.

Quick Start

Run the health check on a project directory to generate a remediation-ready report.

Frequently Asked Questions about Validate Repo

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

FAQPage Schema
How do I run a health check on a Foundry repository structure?

Run the validation against your project directory to check folder structure, required files, and stack-specific tooling, generating a remediation-ready checklist for your Foundry repository.

What files are required to validate a generated Foundry project?

Validating a generated Foundry project checks for the presence of core files like CLAUDE.md and ai/team/composition.yml, ensuring your repository meets the expected structural composition before export.

Does repository linting detect secrets exposure and broken links?

Yes, repository linting detects potential secrets exposure and broken internal links across multiple folders, reporting findings within a pass/fail checklist with actionable remediation steps.

Can I use stack-specific validation for pytest and npm in my project?

Yes, you can run per-stack checks for pytest, npm, and other tooling to verify lint, test, and build commands, receiving remediation guidance for any failures found.

When should I use a repository health check before sharing a project?

Use a repository health check as a pre-export gate before sharing a generated project to ensure folder expectations, template completeness, and link integrity pass validation without exposing secrets.