Build a structured, offline draft of a Yonsei YRI achievement modification request from user-supplied before and after values. Use when a researcher has identified an issue in their own YRI snapshot and wants a reviewable field-level change draft without saving or submitting anything.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add mrcha033/yonsei-skills --skill draft-yri-change --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Draft Yri Change?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mrcha033-draft-yri-change)More formats (shields.io, HTML) on the badges page.
---
name: draft-yri-change
description: Build a structured, offline draft of a Yonsei YRI achievement modification request from user-supplied before and after values. Use when a researcher has identified an issue in their own YRI snapshot and wants a reviewable field-level change draft without saving or submitting anything.
---
# Draft YRI Change
Create a reviewable modification-request draft; never operate YRI.
## Run
Provide `captured_at`, `owner_scope: "self"`, and a `change` object:
```bash
python3 "$SKILL_DIR/scripts/draft_yri_change.py" --input yri-change.json
```
`change` requires `requested_action: "request-modification"`, a `record` with
`record_id`, documented YRI `type`, and `title`, plus `before`, `after`, and a
plain-language `reason`. The offline contract permits changes only to `title`,
`year`, `kri_id`, `issn`, `doi`, and `note`. Optional `attachments` are labels
only; the script does not read files.
Review the generated field-level `changes` and `draft_text`. The output is not
a YRI form payload and must not be described as submitted.
## Boundaries
- Use only the user's own supplied record snapshot.
- Reject submit, send, save, delete, approve, or execute directives.
- Do not change approval state or infer undocumented live-system fields.
- Do not log in, open YRI, write files, or submit a modification request.
Official workflow context:
<https://ysrnd.yonsei.ac.kr/main/noticeDetail.do?key=262&type=YRI>
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.