Skip to content
Back to skills

Summarize Rms Project

ASecurity

Normalize a user-provided Yonsei RMS JSON or Excel-transcribed project snapshot into a privacy-minimized summary of project identity, period, budget, participant counts, and supplied workflow state. Use when a researcher needs an offline project overview without querying or changing RMS.

  • 8 stars
  • 0 votes
  • 0 copies
  • 2 views
  • 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 summarize-rms-project --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Summarize Rms Project?

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

Security grade badge for Summarize Rms Project
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mrcha033-summarize-rms-project/badge)](https://www.skillsdirectory.com/skills/mrcha033-summarize-rms-project)

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: summarize-rms-project
description: Normalize a user-provided Yonsei RMS JSON or Excel-transcribed project snapshot into a privacy-minimized summary of project identity, period, budget, participant counts, and supplied workflow state. Use when a researcher needs an offline project overview without querying or changing RMS.
---

# Summarize RMS Project

Summarize one supplied RMS project snapshot and expose internal contradictions.

## Run

Provide `captured_at`, optional `source_format`, and a `project` object:

```bash
python3 "$SKILL_DIR/scripts/summarize_rms_project.py" --input rms-project.json
```

The declared `project` contract requires `project_code`, `title`, `status`,
`period` (`start_date`, `end_date`), `budget` (`currency`, `total`, `executed`,
optional `committed` and `remaining`), `workflow` (`stage`, optional
`pending_action`), and `participants`. Each participant needs a pseudonymous
`participant_key`, `role`, and optional `status`. Do not include names or
institutional identifiers.

Amounts may be JSON numbers or decimal strings and are returned as decimal
strings. Review `issues` and `complete`; the workflow values remain the
snapshot's opaque labels, not interpreted live states.

## Boundaries

- Process only user-supplied JSON or Excel-transcribed data.
- Reject credentials, government identifiers, bank accounts, and tax identifiers.
- Do not query RMS, infer undocumented fields, or expose participant keys in output.
- Do not save, approve, submit, or alter any project or workflow.

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.yaml210 B
  • scripts/summarize_rms_project.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.