config
Skill1 starsChanged 3 months agoMITView on GitHub
Use when adding an environment variable, base URL, credential, or environment-driven setting, or when wiring multi-environment runs. Single source of truth for URLs and secrets.
- Reads credentials
25 other projects use a version of this.
Adopted by
Most recently taken up by
- brquatti/readme-styletheir own version, first seen Nov 15, 2026
- idavidov13/agentic-playwrighttheir own version, first seen Nov 8, 2026
- nearmap/shipyardtheir own version, first seen Nov 8, 2026
- Dariusplayer09/adaptive-skillstheir own version, first seen Nov 8, 2026
- aarontzeng/dev-leadtheir own version, first seen Nov 5, 2026
- adyusuf/claude-code-standardstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use uninstall.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkilluninstall
Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.
Also in 3 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- microsoft/TokenEconomizer★ 6.2ksame name
- orangehrm/orangehrm★ 1.1ksame name
- idavidov13/agentic-playwright★ 294same name
- leonardcser/cursortab.nvim★ 265same name
- tmck-code/yet-another-statusline★ 244same name
- genkovich/sdd★ 187same name
- ThisisYoYoDev/claude-rag★ 9same name
- JeremieSamson/green-code★ 7same name
- dungnotnull/black-garlic-fermentation-optimization-agent-skill★ 5same name
- dungnotnull/standalone-solar-deep-station-agent-skill★ 5same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- ai-native-workflowSkill
- api-testingSkill
- bootstrapSkill
- common-tasksSkill
- data-strategySkill
- debuggingSkill
- enumsSkill
- fixturesSkill
- page-objectsSkill
- salesforce-authSkill
- salesforce-dataSkill
- salesforce-locatorsSkill
- salesforce-metadata-contractSkill
- salesforce-personasSkill
- salesforceSkill
- salesforce-waitsSkill
- security-testingSkill
- selectorsSkill
- test-standardsSkill
- type-safetySkill
- wait-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 30
Add new vars to env/.env.<env>.example (and your real env file) so the contract is documented.
- Very specific: line 31
Read via appConfig.* (which reads process.env.* with ??
- Very specific: line 33
Add a typed appConfig property only if the value is reused or needs a guard.
- Distinctive: line 34
Never commit a real secret.
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Config & Environments
URLs and credentials come from the environment, never hardcoded.
Loading
playwright.config.ts reads ENVIRONMENT (default dev) and loads env/.env.<environment> via
dotenv. Files: env/.env.dev, .env.staging, .env.prod, .env.ci — all gitignored; only
*.example is tracked.
ENVIRONMENT=staging npx playwright test # loads env/.env.stagingWhere a value belongs
| Value | Home |
| Base URL, API URL, credentials, env-driven setting | process.env.*, surfaced via config/app.config.ts |
| Endpoint path, route, UI message | enums/ (NOT config) |
Rules
BASE_URLis the app ROOT only — never bake in a path (e.g..../todomvc), or agoto('/')drops it. Path segments belong inenums/util/routes.ts; navigate to them.- Add new vars to
env/.env.<env>.example(and your real env file) so the contract is documented. - Read via
appConfig.*(which readsprocess.env.*with??fallback or therequired()guard). Neverprocess.env.X as string. - Add a typed
appConfigproperty only if the value is reused or needs a guard; otherwise readprocess.env.*directly. - Never commit a real secret. Never print a credential to the console/report.
CI
CI=1 is set in GitHub Actions; appConfig.isCI and playwright.config.ts use it to enable retries
and the GitHub reporter. Replay CI locally: npm run test:ci.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

