Search and filter current official Yonsei University and Sinchon IT service notices, with inclusive publication-date ranges, global cross-source sorting, publisher metadata, excerpts, and direct official links. Use for requests such as finding Yonsei announcements about scholarships, tuition, registration, accounts, security, outages, or notices published during a specific period.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add mrcha033/yonsei-skills --skill search-yonsei-notices --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Search Yonsei Notices?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mrcha033-search-yonsei-notices)More formats (shields.io, HTML) on the badges page.
---
name: search-yonsei-notices
description: Search and filter current official Yonsei University and Sinchon IT service notices, with inclusive publication-date ranges, global cross-source sorting, publisher metadata, excerpts, and direct official links. Use for requests such as finding Yonsei announcements about scholarships, tuition, registration, accounts, security, outages, or notices published during a specific period.
---
# Search Yonsei Notices
Run the plugin-local deterministic search:
```bash
python3 "$SKILL_DIR/scripts/search_yonsei_notices.py" \
--source all \
--contains "장학" \
--from 2026-07-01 \
--to 2026-07-31 \
--limit 20
```
Omit filters the user did not request. Treat `--from` and `--to` as inclusive publication dates. Use `--source university` or `--source it` only when the user narrows the board.
Read the JSON `partial` and `errors` fields before reporting results. Return each notice's title, publisher, publication date, and official URL. Distinguish the publication date from any event date mentioned in the title or excerpt.
Do not claim that absence from the bounded official source window proves that no older notice exists. Do not use credentials, VPN, reposts, or search-result snippets.
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.