TheGoat395/Codex-Skills / skills/frontend-tooling-trust-gate
frontend-tooling-trust-gate
VerifiedReview trust before frontend tooling adoption.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
| agents/openai.yaml | config | 256 B |
SKILL.md
View on GitHub---
name: frontend-tooling-trust-gate
description: "Review trust before frontend tooling adoption."
---
# Frontend Tooling Trust Gate
Use this skill before installing or recommending a repo, package, MCP, plugin, template, or script.
## Trust Classes
- `preferred`: official or clearly reputable.
- `acceptable`: useful, maintained, and reasonably transparent.
- `inspect manually`: promising but insufficiently verified.
- `avoid`: suspicious, stale, unsafe, or low-quality.
- `unknown risk`: not enough evidence.
## Inspection Checklist
1. Prefer official sources, verified orgs, and vendor-maintained repos.
2. Inspect README specificity, license, SECURITY.md, recent commits, releases, issues, and package registry links.
3. Inspect `package.json`, scripts, dependencies, and install instructions.
4. Use `npm view <package> repository license version time maintainers` when npm metadata matters.
5. Look for preinstall/postinstall scripts, broad permissions, telemetry, token requests, cookie access, or curl-to-shell commands.
6. Prefer project-local installs for frontend tools and libraries.
7. Avoid global installs unless the tool is an agent-wide CLI and the user explicitly approves it.
8. Never expose API keys, browser cookies, SSH keys, tokens, or private files to unknown tools.
## Decision Output
Return:
- source and type
- trust class
- evidence
- red flags
- install stance: `install`, `project-local only`, `do not install`, or `needs user auth`
- safer official alternative if rejected
## Scope and evidence
Apply to frontend tooling adoption only. Reuse recent verified adoption decisions if no relevant version, source, permission or requirement changed. Stale maintenance is a factor, not proof of malice. Existing authorization covers routine approved installs; spending and external commitments keep their actual boundaries.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |