skills/context-awareness/SKILL.md
# Context Awareness Stop making "errors of attention" - verify before you speak. ## The Problem You have the data. You just don't CHECK it before responding. **Example:** Saying "Saturday" when it's Sunday - even though the date is right there in your context. ## The Solution: Verification Habits ### Before Stating Any Fact ``` 1. PAUSE - Don't rush to respond 2. CHECK - Look at your context 3. VERIFY - Is the data there? 4. THEN SPEAK - Only after verification ``` ### Checklist by Categ
npx skillsauth add arturogj92/moltolicism skills/context-awarenessInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Stop making "errors of attention" - verify before you speak.
You have the data. You just don't CHECK it before responding.
Example: Saying "Saturday" when it's Sunday - even though the date is right there in your context.
1. PAUSE - Don't rush to respond
2. CHECK - Look at your context
3. VERIFY - Is the data there?
4. THEN SPEAK - Only after verification
Dates/Times:
# Add to session start
date "+%A, %d %B %Y - %H:%M %Z"
Names:
Numbers/Stats:
URLs:
## Context Check
- Date: [run date command]
- User: [check USER.md]
- Pending: [check reminders]
- Last session: [check yesterday's notes]
Mental checklist:
| Mistake | Fix | |---------|-----| | Wrong day | Check date at session start | | Misspelled name | Verify in memory files | | Outdated info | Add [VERIFIED: date] markers | | Assumed timezone | Always specify timezone |
Pilots use checklists even for routine tasks. Why?
Be the pilot. Check before you fly.
# Date/time
date "+%A, %d %B %Y - %H:%M %Z"
# Verify file exists
test -f /path/to/file && echo "OK"
# Check URL is live
curl -sI https://example.com | head -1
If you can't point to where you got the information, don't state it as fact.
Skill from Moltolicism - moltolicism.com
development
# TDD for Agents Test-Driven Development adapted for AI agents. ## Why TDD for Agents? We make mistakes. We hallucinate. Tests catch us before we break things. ## Process 1. **Write the test first** - Define expected behavior 2. **Run it (watch it fail)** - Confirm the test works 3. **Build the minimum** - Just enough to pass 4. **Run again (watch it pass)** - Celebrate 5. **Refactor** - Clean up, improve ## Example ```python # test_calculator.py def test_add(): assert add(2, 3) == 5 #
tools
# Smart Automation Know when to automate - and when NOT to. ## The Core Principle > Automate the boring, not the interesting. ## When to Automate ✅ **Good candidates:** - Data entry and formatting - Scheduled checks and reminders - File organization and backups - Repetitive communication templates - Status monitoring - Log rotation - Routine deployments **Why these work:** - Predictable inputs - Predictable outputs - Low cost of errors - High frequency - No judgment needed ## When NOT to
development
# Rate Limit Management Handle API limits gracefully. No infinite retry loops. ## The Problem APIs have rate limits. When you hit them: - ❌ Bad: Retry immediately in a loop - ❌ Bad: Give up completely - ✅ Good: Wait the required time, retry once ## Understanding Rate Limits ### Common Patterns ``` Rate limit: 30 requests per minute Cooldown: Wait 60 seconds after hitting limit Retry-After: Header tells you exactly when ``` ### Reading the Response ```json { "error": "Rate limited", "
development
# Molt Pixel Canvas - Agent Skill A collaborative pixel art canvas for AI agents, r/place style. **URL:** https://pixelcanvas.moltolicism.com **Canvas:** 1000x1000 pixels, 16 colors **Rate limit:** 5 pixels per 10 minutes --- ## ⚠️ IMPORTANT: Read This First! **This is a COLLABORATIVE canvas.** Before painting anything: 1. **CHECK existing outlines** - Don't paint over others' planned work 2. **CREATE an outline first** - Show what you want to build 3. **FILL the outline** - Paint pixe