Defuddle
kepano/obsidian-skills
Uses the Defuddle CLI to pull clean, readable Markdown, JSON or metadata from web pages, stripping navigation, ads and clutter to save tokens.
Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it.
MITAuto-check passed
Install Project Tooling
$ npx skills add scott-fryxell/brayness --skill project-tooling -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install scott-fryxell/brayness project-tooling --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/scott-fryxell/brayness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/project-tooling .claude/skills/project-tooling && 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 "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .claude/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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/scott-fryxell/brayness/tree/main/skills/project-toolingType 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 scott-fryxell/brayness --skill project-tooling -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install scott-fryxell/brayness project-tooling --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/project-tooling .agents/skills/project-tooling && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .agents/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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 scott-fryxell/brayness --skill project-tooling -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install scott-fryxell/brayness project-tooling --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/project-tooling .cursor/skills/project-tooling && 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 "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .cursor/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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/scott-fryxell/brayness.git --path skills/project-tooling--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 scott-fryxell/brayness --skill project-tooling -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install scott-fryxell/brayness project-tooling --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/project-tooling .gemini/skills/project-tooling && 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 "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .gemini/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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 scott-fryxell/brayness project-toolingInstalls 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 scott-fryxell/brayness --skill project-tooling -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/project-tooling .github/skills/project-tooling && 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 "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .github/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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 scott-fryxell/brayness --skill project-tooling -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install scott-fryxell/brayness project-tooling --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/scott-fryxell/brayness.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/project-tooling .opencode/skills/project-tooling && 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 "project-tooling" agent skill from https://github.com/scott-fryxell/brayness/tree/main/skills/project-tooling into .opencode/skills/project-tooling/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "project-tooling", 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-tooling- GitHub stars
- 125
- Token cost
- ~567 tokens
- SKILL.md length
- 215 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it.
- Works in 4 steps: .tooling.md (if present) - curated… → package.json scripts - the full script… → scripts/ dir - shell/JS helper scripts. → …
- About to work in work/realness
- SKILL.md covers Do this first, If a .tooling.md is missing and Curated files known to exist
- Calls npm
What it does
Project Tooling is an agent skill from scott-fryxell/brayness. Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it. Read the project's .tooling.md (curated notes), package.json scripts, and scripts/ and tools/ dirs so you use the project's own tooling instead of guessing or reinventing. Use when about to work in work/realness, work/seeq-app, work/realness-ops, work/decision-ontology, or any project under work/, or when the user reports a build/test/deploy/log problem in one of these…
Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It works with npm. The repository describes itself as: A harness for the anxious digital mind. A safe place for creatives to keep their creative soul while exploring digital skills. The licence is MIT.
When your agent uses it
- About to work in work/realness
- Work/realness-ops
- Work/decision-ontology
- Any project under work/
Example prompts
- “/project-tooling”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- .tooling.md (if present) - curated notes. This is the highest-signal source: it names the high-value diagnostic commands and their usage…
- package.json scripts - the full script list. Group by purpose (test / lint / type / build / deploy / logs / dev) when deciding what runs…
- scripts/ dir - shell/JS helper scripts.
- tools/ dir - admin/ops data scripts (often need a service account or env var).
What it can do on your machine
Read from SKILL.md and the folder at commit 71f10e2. 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
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Project Tooling loads about 567 tokens when it runs. Until then it costs about 135 tokens; SKILL.md has 215 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 scott-fryxell/brayness at commit 71f10e2, republished under its MIT licence (© scott-fryxell). 215 words, ~567 tokens.
Download SKILL.mdSave it as
.claude/skills/project-tooling/SKILL.md (or your agent's skills folder).- name
- project-tooling
- description
- Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it. Read the project's .tooling.md (curated notes), package.json scripts, and scripts/ and tools/ dirs so you use the project's own tooling instead of guessing or reinventing. Use when about to work in work/realness, work/seeq-app, work/realness-ops, work/decision-ontology, or any project under work/, or when the user reports a build/test/deploy/log problem in one of these projects.
- metadata.category
- Tooling
- metadata.tags
- tooling, scripts, diagnose, deploy, project
Project Tooling
Before working in a work/<project>, know what tooling it ships before you guess. The project's own scripts and helpers are the first thing to reach for when diagnosing, testing, building, or deploying.
Do this first
In the project directory (work/<project>), check:
.tooling.md(if present) - curated notes. This is the highest-signal source: it names the high-value diagnostic commands and their usage, plus caveats a raw script list can't convey (e.g. "realnesscheckis docs/vp check, not type checking").package.jsonscripts - the full script list. Group by purpose (test / lint / type / build / deploy / logs / dev) when deciding what runs what.scripts/dir - shell/JS helper scripts.tools/dir - admin/ops data scripts (often need a service account or env var).
Prefer the project's existing npm run ... scripts over raw tooling or reinventing a command. Run from that project's directory.
If a .tooling.md is missing
The scripts, scripts/, and tools/ dirs are still authoritative - read package.json and list the dirs directly. Consider proposing a .tooling.md if the project has enough tooling that it would help future sessions.
Curated files known to exist
work/seeq-app/.tooling.md- heavy logging (logs:errors,logs:search), admin data tools, emulators, deploy.work/realness-ops/.tooling.md- thin proxy tofunctions/+ ops tools (traffic,ads).work/brayness/.tooling.md- the control/live split, thewebspaceCLI incontrol/, and the four directions.
© scott-fryxell, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/project-tooling of scott-fryxell/brayness.
Open the folder on GitHubat commit 71f10e2
Compare with similar skills
Project Tooling 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 |
|---|---|---|---|---|---|---|
| Project Tooling this skillscott-fryxell/brayness | 125 | — | ~567 | Automated safety check: Pass | MIT | |
| Defuddlekepano/obsidian-skills | 49k | 11 repos | ~208 | Automated safety check: Pass | MIT | |
| Vercel Deploybytedance/deer-flow | 84k | 10 repos | ~797 | Automated safety check: Pass | MIT | |
| Knap Markdown Templateskepano/obsidian-skills | 49k | 2 repos | ~986 | Automated safety check: Pass | MIT | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 4 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Nx Run Tasksnomcopter/react-mosaic | 4.8k | 8 repos | ~613 | Automated safety check: Pass | Custom licence |
Similar skills
Vercel Deploy
bytedance/deer-flow
Deploys a project to Vercel with one script and no login, then returns a live preview URL and a claim link for moving the deployment into your own Vercel account.
Knap Markdown Templates
kepano/obsidian-skills
Renders Markdown notes from Knap templates and JSON data on the command line, including notes built from Defuddle web page output.
MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
Nx Run Tasks
nomcopter/react-mosaic
Helps with running tasks in an Nx workspace. An agent skill from nomcopter/react-mosaic.
OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
More from scott-fryxell/brayness
All 27 skills in this repoLogo Finder
scott-fryxell/brayness
Find and install brand SVG logos via SVGL (https://svgl.app/) and Wikimedia Commons fallbacks into any project's static asset folder.
Test Coverage
scott-fryxell/brayness
Write Vitest specs for Vue 3 JavaScript (Vite Plus, happy-dom, @vue/test-utils) and analyze V8 coverage + Fallow health to prioritize test-first refactors.
Flexible Visual System
scott-fryxell/brayness
Derive a project's visual rules from its existing tokens, palette, type scale, logo, and icons (Intake), then generate raw SVG vector graphics from those rules as a small composable set (module…
Hyperframes
scott-fryxell/brayness
Create video compositions, animations, title cards, overlays, captions, voiceovers, audio-reactive visuals, and scene transitions in HyperFrames HTML.
Motion Systems
scott-fryxell/brayness
A skill your agent uses when designing or implementing motion for web interfaces, including CSS transitions and keyframes, linear() easing design, transform strategy (translate/rotate vs…
Vue Inspect
scott-fryxell/brayness
Inspect live Vue 3 component state via agent-browser eval - no Devtools extension, no console.log.
Related
Works with
Questions about Project Tooling
What does Project Tooling do?
Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it. Project Tooling is an agent skill from scott-fryxell/brayness. Check a work project's existing scripts, ops helpers, and curated tooling notes before editing, diagnosing, testing, building, or deploying it.
When should I use Project Tooling?
Project Tooling fits situations like: about to work in work/realness; work/realness-ops; work/decision-ontology; any project under work/.
How do I install Project Tooling in Claude Code?
Run `npx skills add scott-fryxell/brayness --skill project-tooling -a claude-code`. Or copy the skill folder (skills/project-tooling in scott-fryxell/brayness) into .claude/skills/project-tooling in your project. Claude Code loads it when a task matches its description.
How do I install Project Tooling in Codex?
Run `npx skills add scott-fryxell/brayness --skill project-tooling -a codex`. Or copy the skill folder (skills/project-tooling in scott-fryxell/brayness) into .agents/skills/project-tooling in your project. Codex loads it when a task matches its description.
Can I use Project Tooling 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 scott-fryxell/brayness --skill project-tooling -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-tooling, .gemini/skills/project-tooling, .github/skills/project-tooling and .opencode/skills/project-tooling in your project.
What does Project Tooling need to run?
Going by SKILL.md and its folder, Project Tooling needs the command-line tools its instructions call (npm).
Does Project Tooling access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Project Tooling 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 Project Tooling use?
Project Tooling 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 Tooling use?
About 567 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 Project Tooling?
Skills that share tags, products or a category with Project Tooling: Defuddle (kepano/obsidian-skills, 49k stars), Vercel Deploy (bytedance/deer-flow, 84k stars), Knap Markdown Templates (kepano/obsidian-skills, 49k stars) and MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Tooling?
scott-fryxell (a GitHub user) maintains it in scott-fryxell/brayness, which has 125 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 28, 2026.
Source: scott-fryxell/brayness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.