Project Validation

Organization

SilentLake-Tech-SkillHub

project-validation

Select and run proportionate validation for project, code, data, AI Agent, document, browser, deployment, Skill, Hook, or management-record changes. Use after implementation and before reporting a stage complete or ready for acceptance.

Overview

Publisher	SilentLake-Tech-SkillHub
Repository	`SilentAgentHub`
Skill name	`project-validation`
Stars	184
Forks	0
Bundled files	2
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by SilentLake-Tech-SkillHub on GitHub. Read the source before you install it.

Installation

Install the Project Validation AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/SilentLake-Tech-SkillHub/SilentAgentHub/tree/main/harness/V5.2.5/skills-source/project-validation
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/SilentLake-Tech-SkillHub/SilentAgentHub/tree/main/harness/V5.2.5/skills-source/project-validation

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/SilentLake-Tech-SkillHub/SilentAgentHub.git /tmp/SilentAgentHub
mkdir -p .claude/skills
cp -r /tmp/SilentAgentHub/harness/V5.2.5/skills-source/project-validation .claude/skills/project-validation

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Project Validation in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Project Validation on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Project Validation is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Project Validation

Select checks

Read the Plan Validation section, module rule, build files, test configuration, CI workflows, and acceptance criteria.
Prefer the project's own commands: make check, make test, make lint, make typecheck, make eval; otherwise infer from package, Python, language, or CI configuration.
Add domain checks: browser paths and console for UI; SQL and data-quality checks for data; evals for prompt, Agent, tool, retrieval, memory, guardrail, model, rubric, or golden-case changes; parser and representative events for Hooks; quick_validate.py for Skills; render-and-readback for documents.
Run the narrowest checks first, then the acceptance path and relevant regression scope.
Capture command, environment, time, result, evidence path, and skipped or unavailable checks.
Update Plan, issue, risk, acceptance, task, and version records consistently.

Validation profiles

Select exactly one profile before running checks. Record the profile and reason.

readonly: questions, status, diagnosis, and readback with no current-turn mutation. Run only targeted readback; do not validate all Skills, Hooks, schemas, manifests, install, or rollback.
simple_change: a low-risk local change with a narrow impact. Parse changed scripts and run targeted smoke/tests only.
complex_engineering: multi-file or behavior changes. Validate changed Skills, changed Hook parsers, targeted E2E, and the relevant regression E2E. Do not run production packaging checks unless releasing.
production_release: only when constructing or promoting a production package. Add all-Skill validation, all-Hook parsing, all schemas, manifest Hash, isolated installation, production smoke, and rollback rehearsal.

Never describe “81 Skill definitions statically validated” as “81 Skills invoked.” Separate semantic Skill usage, static validation targets, Hook scripts executed, and files hashed in every report.

For repeated validation, reuse unchanged results within the same commit/worktree Hash and version window. One automatic retry is allowed; after that, use a documented alternative or report the blocker.

Use scripts/check_harness.ps1 for a quick structural audit. Never translate “file exists” into “feature verified”; state verified, failed, unverified, and substitute checks separately.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
scripts/check_harness.ps11 KB

Frequently asked questions

What does the Project Validation AI skill do?

Why use Project Validation on TypingMind?

Because you install it once and use it with any model. Project Validation is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Project Validation in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/SilentLake-Tech-SkillHub/SilentAgentHub/tree/main/harness/V5.2.5/skills-source/project-validation. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Project Validation?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Project Validation?

As many as you like. As long as a model supports skills, you can use Project Validation with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Project Validation AI skill free?

It is published on GitHub by SilentLake-Tech-SkillHub. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gitcrawl

openclaw

OrganizationPopular

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Project Validation

Select checks

Validation profiles

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now