Skip to content
Back to skills

Reminders

ASecurity

List pull-based reminders with the people-context tools. Invoke as /people-context:reminders [person] to see all active reminders, or resolve an optional person first and list only theirs.

  • 56 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 19, 2026
ai-agents

Security analysis

A100/100

Scanned September 19, 2026

npx -y skills add JinyangWang27/people-context --skill reminders --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Reminders?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Reminders
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jinyangwang27-reminders/badge)](https://www.skillsdirectory.com/skills/jinyangwang27-reminders)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: reminders
description: List pull-based reminders with the people-context tools. Invoke as /people-context:reminders [person] to see all active reminders, or resolve an optional person first and list only theirs.
disable-model-invocation: true
argument-hint: "[person] (optional)"
---

# /people-context:reminders

A thin, user-invoked workflow that lists reminders. When the user names a person it
resolves that identity first, then filters; otherwise it lists everything active.

Optional person filter: **$ARGUMENTS**

## Steps

1. **No person given** (the argument above is empty): call `list_reminders` with no
   `person_id`. It returns active reminders, due-dated first and communication notes
   last.

2. **A person is named:** resolve the identity before filtering. Call `resolve_person`
   with the given text, parsing any distinguishing context (organization, role, or
   relationship) into its `hints` (`org`/`role`/`relationship`) rather than leaving it
   in `query` — the name index holds names and aliases, not organizations. Branch on its
   own `ambiguous` flag — not on candidate count. The resolver may return several ranked
   candidates yet report `ambiguous: false` when the top match is confidently ahead.

   - **`ambiguous: false` with at least one candidate:** call `list_reminders` with
     the ranked top candidate's (`candidates[0]`) `person_id`.
   - **`ambiguous: true`:** stop and surface the candidate list so the user can
     choose. Do **not** silently drop the person filter and list everyone's
     reminders, and do not guess a candidate.
   - **Empty candidate list:** report that no one matching is stored rather than
     falling back to an unfiltered list; let the user restate who they mean.

## Boundaries

- Read-only workflow: it calls only `resolve_person` and `list_reminders`. It
  performs no writes.
- It never calls or suggests enabling the gated `get_sensitive_person_context` or
  `export_data` tools.
- Ambiguity is always surfaced; the person filter is never silently discarded.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.