GPT-5 finding
Instruction to use repo description conflicts with security constraint to never copy untrusted content verbatim
- skills/contributor-spotlight/SKILL.md
- skills/contributor-spotlight/SKILL.md
Step 6 suggests using the GitHub repo description, while the Constraints section explicitly forbids copying repo descriptions verbatim. This contradiction can cause unsafe content inclusion or confusion for implementers.
Recommendation
Clarify Step 6 to explicitly paraphrase the existence/theme of the repo without quoting the description. Provide a safe phrasing rule and example (e.g., "a fork focused on X" based on tags or high-level categories) or omit description entirely when uncertain.