Skip to content
Back to skills

Check Rms Participants

ASecurity

Check a privacy-minimized, user-provided Yonsei RMS participant snapshot for project-period bounds, duplicate assignments, missing allocation data, and overlapping allocation above 100 percent. Use when a researcher wants an offline participant consistency review without querying or changing RMS.

  • 8 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 1, 2026
ai-agentspythongobash

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 1, 2026

npx -y skills add mrcha033/yonsei-skills --skill check-rms-participants --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Check Rms Participants?

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

Security grade badge for Check Rms Participants
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mrcha033-check-rms-participants/badge)](https://www.skillsdirectory.com/skills/mrcha033-check-rms-participants)

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: check-rms-participants
description: Check a privacy-minimized, user-provided Yonsei RMS participant snapshot for project-period bounds, duplicate assignments, missing allocation data, and overlapping allocation above 100 percent. Use when a researcher wants an offline participant consistency review without querying or changing RMS.
---

# Check RMS Participants

Check declared participant periods and allocations within one supplied project.

## Run

Provide `captured_at`, `project_code`, `project_period`, and `participants`:

```bash
python3 "$SKILL_DIR/scripts/check_rms_participants.py" --input rms-participants.json
```

`project_period` and every participant assignment use ISO `start_date` and
`end_date`. Each assignment requires a locally chosen, pseudonymous
`participant_key` and `role`; `status` and `allocation_percent` are optional.
Do not include names, contact details, student or employee IDs, government
identifiers, or financial identifiers.

The checker reports assignments outside the project period, exact duplicate
assignments, and overlapping supplied allocations above 100 percent. Missing
allocation values remain in `unknowns`; they are never guessed.

## Boundaries

- Process only user-supplied JSON or Excel-transcribed data.
- Treat role and status labels as opaque snapshot values; do not infer RMS policy.
- Reject credentials and direct identifiers rather than echoing them.
- Do not invite, remove, approve, save, or submit a participant change.

Official manual context:
<https://research.yonsei.ac.kr/research/data_manual.do?articleNo=114666&mode=view>

Files in this skill

  • SKILL.md1.6 KB
  • agents/openai.yaml247 B
  • scripts/check_rms_participants.py9.5 KB

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.