Vc Problem Solving
withkynam/vibecode-pro-max-kit
Apply systematic problem-solving techniques when stuck. An agent skill from withkynam/vibecode-pro-max-kit.
Find how this problem is already solved: standards we could adopt, and the industry's best practices.
MITAuto-check passed
Install Find Standards
$ npx skills add will-ness-ai/skills --skill find-standards -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install will-ness-ai/skills find-standards --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/find-standards .claude/skills/find-standards && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .claude/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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.
$skill-installer install https://github.com/will-ness-ai/skills/tree/main/skills/find-standardsType 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.
$ npx skills add will-ness-ai/skills --skill find-standards -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install will-ness-ai/skills find-standards --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/find-standards .agents/skills/find-standards && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .agents/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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.
$ npx skills add will-ness-ai/skills --skill find-standards -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install will-ness-ai/skills find-standards --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/find-standards .cursor/skills/find-standards && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .cursor/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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.
$ gemini skills install https://github.com/will-ness-ai/skills.git --path skills/find-standards--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add will-ness-ai/skills --skill find-standards -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install will-ness-ai/skills find-standards --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/find-standards .gemini/skills/find-standards && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .gemini/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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.
$ gh skill install will-ness-ai/skills find-standardsInstalls 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).
$ npx skills add will-ness-ai/skills --skill find-standards -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/find-standards .github/skills/find-standards && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .github/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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.
$ npx skills add will-ness-ai/skills --skill find-standards -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install will-ness-ai/skills find-standards --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/will-ness-ai/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/find-standards .opencode/skills/find-standards && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "find-standards" agent skill from https://github.com/will-ness-ai/skills/tree/main/skills/find-standards into .opencode/skills/find-standards/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "find-standards", 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
find-standards- GitHub stars
- 168
- Token cost
- ~585 tokens
- SKILL.md length
- 346 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Find how this problem is already solved: standards we could adopt, and the industry's best practices.
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Find Standards is an agent skill from will-ness-ai/skills. Find how this problem is already solved: standards we could adopt, and the industry's best practices.
Its SKILL.md is about 590 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: Skills for building high quality software. The licence is MIT.
Example prompts
- “/find-standards”
What it can do on your machine
Read from SKILL.md and the folder at commit 71d8909. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Find Standards loads about 585 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 346 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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.
SKILL.md
The full file from will-ness-ai/skills at commit 71d8909, republished under its MIT licence (© will-ness-ai). 346 words, ~585 tokens.
Download SKILL.mdSave it as
.claude/skills/find-standards/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- find-standards
- description
- Find how this problem is already solved: standards we could adopt, and the industry's best practices.
- disable-model-invocation
- true
Our #1 goal when desiging software is to keep our codebase and ecosystem small and design changes by analyzing tradeoffs around code, design, domain, dependencies, and/or infrastructure. We need to consider if we should:
- Adapt existing patterns
- Adopt new patterns
- Replace existing pattern because it is outdated or bad design or just no longer works for us.
Find how the problem in front of the user is already solved, and /research two things:
- Standards we could adopt (Internal): What do we already do that is applicable to this problem? What would the solution for this problem look like in our current codebase minimizing new code and dependencies?
- Best practices (External): how the industry solves this, and the problem each practice solves.
Fan out subagents in one batch, one per angle, and cover sources below to generate an extremely detailed response (written after Skill tool call for writing-for-agents). Each subagent starts blank, so give it a description of the problem and what its trying to find. The subagents read; you judge what comes back, and report.
Examples of things the agents could consider: code patterns, libraries, standards, best practices, design/component choices, page structure, api structure, design patterns, resources and write-up by teams who hit this at scale. Prioritize evidence/proof and reputable sources.
Every standard names a real artifact: a library, a file path with lines, a spec, an article, a doc URL. "Use a state machine" is not a finding; xstate and src/order/machine.ts:40 are. Every practice names the problem it solves, so we can tell whether we have that problem.
Report one table: each candidate, what it is, where it is already in use, and what it costs us to take. Show us both the internal and external for each candidate (leave blank if nothing was reported). Then give your recommended default, and the one fact that would change it.
Done when both sources have reported, and each candidate carries a verdict: adopt, adapt, or ruled out with the reason.
Before getting started, if you have access to a research skill, call the Skill tool for 'research'.
© will-ness-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/find-standards of will-ness-ai/skills.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 71d8909
Compare with similar skills
Find Standards 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Find Standards this skillwill-ness-ai/skills | 168 | — | ~585 | Automated safety check: Pass | MIT | |
| Vc Problem Solvingwithkynam/vibecode-pro-max-kit | 1.1k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Is This A Problemanthropics/claude-for-legal | 9.6k | 2 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Telemetry Standardssupabase/supabase | 111k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Cpp Coding Standardsaffaan-m/ECC | 276k | 4 repos | ~5.6k | Automated safety check: Pass | MIT | |
| Java Coding Standardsaffaan-m/ECC | 276k | 1 repos | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Is This A Problem
anthropics/claude-for-legal
Fast "is this a problem?" answer for the quick Slack question — pattern-matches against your calibration.
- Official
Telemetry Standards
supabase/supabase
PostHog event tracking standards for Supabase Studio. An agent skill from supabase/supabase.
Cpp Coding Standards
affaan-m/ECC
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io).
Java Coding Standards
affaan-m/ECC
Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout.
Resourceful Problem Solving
swarmclawai/swarmclaw
Always-on guidance for solving tasks resourcefully. An agent skill from swarmclawai/swarmclaw.
More from will-ness-ai/skills
Cmux
will-ness-ai/skills
Drive the local cmux app — workspaces, panes, surfaces, terminal input, agent sessions, and browser surfaces.
Sandcastle
will-ness-ai/skills
Run a Sandcastle lane — a sandboxed implement→review loop over a fixed batch of work in its own worktree, ended by an agent-authored PR.
Code Story
will-ness-ai/skills
Build a wizard-style HTML page that teaches how and why a change works.
Flashlight
will-ness-ai/skills
Shine a light into a wayfinder map's fog — work one direction now, out of frontier order, or redraw the map itself.
Test A Skill
will-ness-ai/skills
Field-test a skill by running it cold in parallel agent sessions, then turn what they hit into edits.
Grill Design
will-ness-ai/skills
Converge on a frontend look through rounds of prototypes and grilling verdicts.
Questions about Find Standards
What does Find Standards do?
Find how this problem is already solved: standards we could adopt, and the industry's best practices. Find Standards is an agent skill from will-ness-ai/skills. Find how this problem is already solved: standards we could adopt, and the industry's best practices.
How do I install Find Standards in Claude Code?
Run `npx skills add will-ness-ai/skills --skill find-standards -a claude-code`. Or copy the skill folder (skills/find-standards in will-ness-ai/skills) into .claude/skills/find-standards in your project. Claude Code loads it when a task matches its description.
How do I install Find Standards in Codex?
Run `npx skills add will-ness-ai/skills --skill find-standards -a codex`. Or copy the skill folder (skills/find-standards in will-ness-ai/skills) into .agents/skills/find-standards in your project. Codex loads it when a task matches its description.
Can I use Find Standards 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 will-ness-ai/skills --skill find-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/find-standards, .gemini/skills/find-standards, .github/skills/find-standards and .opencode/skills/find-standards in your project.
What does Find Standards need to run?
SKILL.md names no scripts, command-line tools or credentials: Find Standards is instructions for the agent only.
Does Find Standards access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Find Standards safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Find Standards use?
Find Standards 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 Find Standards use?
About 585 tokens (SKILL.md is roughly 2.3k 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 Find Standards?
Skills that share tags, products or a category with Find Standards: Vc Problem Solving (withkynam/vibecode-pro-max-kit, 1.1k stars), Is This A Problem (anthropics/claude-for-legal, 9.6k stars), Telemetry Standards (supabase/supabase, 111k stars) and Cpp Coding Standards (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Find Standards?
will-ness-ai (a GitHub user) maintains it in will-ness-ai/skills, which has 168 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 9, 2026.
Source: will-ness-ai/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.