| name | youth-safety-review |
| description | Content appropriateness review for FTC student code. Activates when checking variable names, comments, and strings for inappropriate content before sharing. Use when reviewing code that students will see, checking for inappropriate language, or ensuring content is suitable for ages 12-18. |
| license | MIT |
| compatibility | Claude Code, Codex CLI, VS Code Copilot, Cursor |
| metadata | {"author":"ncssm-robotics","category":"tools"} |
| allowed-tools | Read, Glob, Grep |
FTC Youth Safety Review Checks
This skill defines content appropriateness checks for FTC marketplace skills. FTC participants are students ages 12-18, so all content should be appropriate for that audience.
Important: These checks flag items for human review. They do not auto-reject content because context matters. A mentor or maintainer should review flagged items.
Acceptable FTC Terms
These terms are ALLOWED despite potentially triggering filters:
| Term | Context |
|---|
kill, killer | Game mechanic (kill shot, killing it) |
attack, defense | Game strategy terms |
destroy | Game context (destroy opponent's stack) |
target | Vision targeting, game elements |
shoot, shooter | Game mechanisms |
score, scoring | Points and objectives |
dead | Battery dead, dead reckoning |
Language Checks (Warnings)
Flag for human review if detected in:
- Variable names
- Function/method names
- Class names
- Comments
- String literals
- File names
Profanity Detection
Inappropriate Naming
Insensitive Language
Comment Review (Warnings)
Tone and Content
Humor
Personal Information (Errors)
These must be fixed - privacy is important.
Student Information
School Information
Contact Information
Content Appropriateness (Warnings)
Topics to Avoid
Example Content
Severity Levels
| Level | Meaning | Action |
|---|
| Error | Must fix | Personal information, clear violations |
| Warning | Flag for review | Context-dependent, needs human judgment |
| Info | Suggestion | Style improvements |
Review Process
When flagging items:
- Quote the specific content - Show exactly what was flagged
- Explain why - What rule does it potentially violate
- Suggest alternative - Offer appropriate replacement
- Request human review - A mentor should make final call
Example Flags
Flagged (Context Review Needed)
double killer_shot_power = 0.8;
Recommendation: Rename to scoring_shot_power for clarity.
Acceptable (No Flag)
void scoreInHighBasket() { ... }
void driveByDeadReckoning() { ... }
Must Fix (Error)
String studentEmail = "john@school.edu";
Required: Remove personal information.
Running This Review
/review <skill-name> --type youth
Or as part of full review:
/review <skill-name>
See Also
