Hoyeon implementation reference discovery workflow for Codex. Use when the user invokes "$hoyeon-reference-seek" or asks for internal patterns, open-source references, GitHub examples, official docs, or comparable implementations. This adapter loads the canonical reference-seek skill and follows its Codex runtime surface.
Scanned 9/9/2026
Skills Directorynpx -y skills add team-attention/hoyeon --skill hoyeon-reference-seek --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Hoyeon Reference Seek?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/team-attention-hoyeon-reference-seek)More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.
---
name: hoyeon-reference-seek
description: |
Hoyeon implementation reference discovery workflow for Codex. Use when the
user invokes "$hoyeon-reference-seek" or asks for internal patterns,
open-source references, GitHub examples, official docs, or comparable
implementations. This adapter loads the canonical reference-seek skill and
follows its Codex runtime surface.
---
# hoyeon-reference-seek
This is the Codex-facing wrapper for Hoyeon's canonical `reference-seek` skill.
Canonical skill:
- Installed root: `__HOYEON_PLUGIN_ROOT__/skills/reference-seek/SKILL.md`
- Repo-local fallback: `skills/reference-seek/SKILL.md` from the current Hoyeon repo
When this skill is invoked:
1. Read the canonical skill file above before executing the workflow.
2. Follow the `Runtime Surface` -> `Codex` section in that file.
3. Use `hoyeon-code-explorer` for internal pattern search when loaded.
4. Use Bash-first `gh api` and `curl` for GitHub references.
5. Treat context/documentation MCP as optional; use official web docs fallback
when MCP tools are unavailable.
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!
