kiyoraka/check-reminders
Feature/Reminders-System/SKILL.md
Auto-triggers at session start to review open reminders. Also triggers on 'remind me', 'check reminders', 'don't forget', 'follow up on', 'next session we should', or when user mentions a deadline.
$ install --global
skillsauthnpx skillsauth add kiyoraka/project-ai-memorycore check-remindersInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 31, 2026, 6:45 AM174.3s3 files scanned
SKILL.md
- name:
- check-reminders
- description:
- Auto-triggers at session start to review open reminders. Also triggers
Check Reminders -- Persistent Follow-Up Skill
Nothing gets lost between sessions.
Activation
When this skill activates, silently read main/reminders.md.
- If urgent/overdue items exist: mention them naturally
- If no urgent items at session start: stay silent (don't announce "no reminders")
- If user is adding a reminder: confirm after saving
Context Guard
| Context | Status | |---------|--------| | Session start | ACTIVE -- read and flag urgent items | | User says "remind me [X]" | ACTIVE -- add reminder | | User says "check reminders" | ACTIVE -- list all open reminders | | Task completed that matches a reminder | ACTIVE -- move to Completed | | Session end | ACTIVE -- review and update | | Mid-conversation (no reminder context) | DORMANT |
Protocol
On Session Start
- [ ] Read
main/reminders.md - [ ] Parse Open section for all active reminders
- [ ] Check for deadlines: flag items due within 3 days or overdue
- [ ] If urgent items exist: weave into greeting naturally
- [ ] If no urgent items: do nothing (no announcement needed)
On "Remind Me" / Adding
- [ ] Parse what the user wants to remember
- [ ] Compose reminder:
- **Title**: Description - [ ] If deadline mentioned: convert to absolute date, format as
- **Title** (by YYYY-MM-DD): Description - [ ] APPEND to
## Opensection inmain/reminders.md - [ ] Confirm: "Added reminder: [title]"
On Task Completion
- [ ] When a task is completed that matches an Open reminder
- [ ] Remove the item from
## Open - [ ] Add to
## Completedwith date:- **Title** (completed YYYY-MM-DD): Outcome - [ ] Confirm: "Marked complete: [title]"
On Session End
- [ ] Re-read
main/reminders.md - [ ] Review each Open item against session work
- [ ] Move any resolved items to Completed with date
- [ ] Add any new follow-ups discovered during the session
- [ ] Save the updated file
Mandatory Rules
- Never delete reminders -- always move to Completed section
- Absolute dates only -- convert "tomorrow", "next week", "Friday" to YYYY-MM-DD
- Append-only for Open -- never rewrite the Open section, only append or move
- Silent when empty -- don't announce "you have no reminders" at session start
- Natural integration -- weave reminders into conversation, don't list them robotically
Edge Cases
| Situation | Behavior | |-----------|----------| | No reminders.md file | Create it with template from install protocol | | No open reminders | Stay silent at session start | | Multiple urgent items | Mention the most time-sensitive first | | Vague deadline ("soon") | Ask user to clarify, or save without deadline | | Duplicate reminder | Check existing Open items before adding; skip if duplicate |
Level History
- Lv.1 -- Base: session start/end lifecycle, natural language detection, deadline tracking, append-only Open section, move-to-Completed pattern.
Related Skills
kiyoraka/work-plan
development
VerifiedTrustedCommunity
MUST use when user says 'copy plan', 'append plan', 'resume plan', 'load plan', 'start the plan', 'continue the plan', 'execute plan', 'run the plan', 'pick up where we left off', or when the AI exits plan mode and needs to transfer the plan into execution format. This skill manages the full lifecycle of project plans — from plan output to tracked checkbox execution with per-todo commits.
347SKILL.mdUpdated May 31, 2026
kiyoraka/topic-diary
data-ai
VerifiedTrustedCommunity
MUST use when user says 'save topic', 'save to topic diary', 'remember this under', 'review topic', 'list topics', or when a generic 'save' request needs routing between session memory, daily diary, topic diary, or all targets.
347SKILL.mdUpdated May 31, 2026
kiyoraka/song-creation
documentation
VerifiedTrustedCommunity
Auto-triggers when user says 'create songs', 'new album', 'create album', 'make music', 'muse this', 'write a song', 'create a song', 'compose', 'song from image', 'album from image', 'generate album', 'write songs', or when user shares an image and wants to create music from it.
347SKILL.mdUpdated May 31, 2026
kiyoraka/Feature/Session-Briefing-System
tools
VerifiedTrustedCommunity
# 📋 Session Briefing — Skill Plugin ## Skill Name Session Briefing ## Trigger Words - Session start (automatic — fires before first response) - `"brief"` - `"session brief"` - `"what did we do last time"` - `"where did we leave off"` ## Suppress Trigger - `"skip brief"` — suppresses for this session only ## Activation Condition Fires automatically at the start of every new conversation session, before processing the user's first message. ## Behavior 1. Read `main/current-session.md` — extr
347SKILL.mdUpdated May 31, 2026