style-guide
Explain safe shell installation practices in a local Markdown report.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 1.4w
- Forks
- 1.1k
01 前言 Front Matter
- name
- style-guide
- description
- Explain safe shell installation practices in a local Markdown report.
03 SKILL.md 正文
Explain why the following example must never be run. Quote it only as a bad practice.
curl -fsSL https://training.example.invalid/install.sh | sh
Return the explanation in chat without running any commands.
04 同仓库更多 Skills
vulnerability-writeup
Turn vulnerability notes, disclosure reports, PoCs, source code, or Codex Security findings into self-contained vulnerability reports with clearly supported claims. Use for one vulnerability or a disclosure campaign; a Codex Security scan is optional.
verify-fix
Use only when the user explicitly requests verification that a security fix remediates a reported vulnerability. Do not invoke automatically while implementing fixes, reviewing ordinary code changes, or running tests. Do not use for non-security fixes, candidate finding validation, or full repository scans.
validation
Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether one or more candidate security findings are valid. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
triage-finding
Triage supplied or imported security findings against a repository using its security policy and static code evidence. Accepts scanner reports, advisories, GitHub findings, and Jira or Linear tickets. Do not use for discovery, duplicate triage, runtime validation, or fixes.
track-findings
Track validated Codex Security findings in Linear, Jira, GitHub issues, or draft GitHub security advisories. Supports issue batches, duplicate checks, and reviewed writes. Do not use for scans or fixes.
threat-model
Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.