Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .claude/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .agents/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .cursor/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .gemini/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .github/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "project-guidelines-example" agent skill from https://github.com/vibeeval/vibecosystem/tree/main/skills/project-guidelines-example into .opencode/skills/project-guidelines-example/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-guidelines-example", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
project-guidelines-example
GitHub stars
531
Used in
3 other repos
Token cost
~2.2k tokens
SKILL.md length
238 words
Files
1
Skills in repo
144
Repo updated
First seen
Licence
MIT
At a glance
Example template for project-specific skill files covering architecture, patterns, testing, and deployment.
Works in 8 steps: No emojis in code, comments, or… → Immutability - never mutate objects or… → TDD - write tests before implementation → …
Tasks that involve Software architecture
SKILL.md covers When to Use, Architecture Overview, File Structure and Code Patterns, plus 4 more sections
Calls npm, poetry and gcloud; reaches xxx.supabase.co; needs NEXT_PUBLIC_SUPABASE_ANON_KEY and ANTHROPIC_API_KEY
What it does
Project Guidelines Example is an agent skill from vibeeval/vibecosystem. Example template for project-specific skill files covering architecture, patterns, testing, and deployment.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in AI & LLM Engineering, covering Software architecture, Structured output and tool calling and Deployment. The repository describes itself as: AI software team for Claude Code - 138 agents, 295 skills, 73 hooks. Self-learning, multi-agent swarm, autonomous skill evolution. The licence is MIT.
When your agent uses it
Tasks that involve Software architecture
Tasks that involve Structured output and tool calling
Tasks that involve Deployment
Example prompts
“/project-guidelines-example”
Requirements
Python 3
A credential in NEXT_PUBLIC_SUPABASE_ANON_KEY
A credential in ANTHROPIC_API_KEY
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
1No emojis in code, comments, or documentation
2Immutability - never mutate objects or arrays
3TDD - write tests before implementation
480% coverage minimum
5Many small files - 200-400 lines typical, 800 max
6No console.log in production code
7Proper error handling with try/catch
8Input validation with Pydantic/Zod
What it can do on your machine
Read from SKILL.md and the folder at commit 3b763b1. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
poetry
gcloud
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
xxx.supabase.co
Also links to:
zenith.chat
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
NEXT_PUBLIC_SUPABASE_ANON_KEY
ANTHROPIC_API_KEY
SUPABASE_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Project Guidelines Example loads about 2.2k tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 238 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~34
When it runs· the whole SKILL.md, loaded when a task matches
~2.2k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NoteMentions a .env fileSKILL.md:318
# Frontend (.env.local)
NoteMentions a .env fileSKILL.md:323
# Backend (.env)
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
# Run all tests
poetry run pytest tests/
# Run with coverage
poetry run pytest tests/ --cov=. --cov-report=html
# Run specific test file
poetry run pytest tests/test_auth.py -v
Test structure:
python
import pytest
from httpx import AsyncClient
from main import app
@pytest.fixture
async def client():
async with AsyncClient(app=app, base_url="http://test") as ac:
yield ac
@pytest.mark.asyncio
async def test_health_check(client: AsyncClient):
response = await client.get("/health")
assert response.status_code == 200
assert response.json()["status"] == "healthy"
Frontend (React Testing Library)
bash
# Run tests
npm run test
# Run with coverage
npm run test -- --coverage
# Run E2E tests
npm run test:e2e
# Build and deploy frontend
cd frontend && npm run build
gcloud run deploy frontend --source .
# Build and deploy backend
cd backend
gcloud run deploy backend --source .
We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in vibeeval/vibecosystem, which our catalogue first saw on October 7, 2026.
Project Guidelines Example next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Project Guidelines Example compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Project Guidelines Example this skillvibeeval/vibecosystem
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management", or needs ADK (Agent…
Deploy LLM models on OCI using AI Quick Actions (AQUA) - single model, multi-model, stacked (LoRA), with GPU shape selection, vLLM configuration, streaming, and tool calling.
A skill your agent uses when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server —…
Example template for project-specific skill files covering architecture, patterns, testing, and deployment. Project Guidelines Example is an agent skill from vibeeval/vibecosystem. Example template for project-specific skill files covering architecture, patterns, testing, and deployment.
When should I use Project Guidelines Example?
Project Guidelines Example fits situations like: tasks that involve Software architecture; tasks that involve Structured output and tool calling; tasks that involve Deployment.
How do I install Project Guidelines Example in Claude Code?
Run `npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a claude-code`. Or copy the skill folder (skills/project-guidelines-example in vibeeval/vibecosystem) into .claude/skills/project-guidelines-example in your project. Claude Code loads it when a task matches its description.
How do I install Project Guidelines Example in Codex?
Run `npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a codex`. Or copy the skill folder (skills/project-guidelines-example in vibeeval/vibecosystem) into .agents/skills/project-guidelines-example in your project. Codex loads it when a task matches its description.
Can I use Project Guidelines Example in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vibeeval/vibecosystem --skill project-guidelines-example -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/project-guidelines-example, .gemini/skills/project-guidelines-example, .github/skills/project-guidelines-example and .opencode/skills/project-guidelines-example in your project.
What does Project Guidelines Example need to run?
Going by SKILL.md and its folder, Project Guidelines Example needs the command-line tools its instructions call (npm, poetry and gcloud) and credentials named NEXT_PUBLIC_SUPABASE_ANON_KEY, ANTHROPIC_API_KEY and SUPABASE_KEY. Our summary lists: Python 3; A credential in NEXT_PUBLIC_SUPABASE_ANON_KEY; A credential in ANTHROPIC_API_KEY.
Does Project Guidelines Example access the network?
SKILL.md names 2 domains. In commands or code: xxx.supabase.co; the agent is likely to contact it when it follows the instructions. As links in the text: zenith.chat. This is read from the text; nothing was executed.
Is Project Guidelines Example safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Project Guidelines Example use?
Project Guidelines Example is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Guidelines Example use?
About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Project Guidelines Example?
Skills that share tags, products or a category with Project Guidelines Example: Google Agents CLI Adk Code (pifferologo/cloud-agents-cli, 129 stars), Aqua Deployment (oracle/accelerated-data-science, 125 stars), Langchain (Orchestra-Research/AI-Research-SKILLs, 13k stars) and Cc Skill Project Guidelines Example (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Guidelines Example?
vibeeval (a GitHub user) maintains it in vibeeval/vibecosystem, which has 531 GitHub stars. The repository holds 144 skills in this directory. The repository was last updated on August 8, 2026.
Source: vibeeval/vibecosystem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.