Search
team-attention/hoyeon
Skills
Sort:BestMost starsTrending todayTrending this weekTrending this monthNewestRecently updatedName
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | This skill should be used when the user asks to "analyze session", "evaluate skill execution", "check session logs", provides a session ID with a skill path, or wants to verify that a skill executed… | team-attention/ | 173 | — | ~1.9k | Automated safety check: Notes | MIT | 4 mo ago |
| 2 | Recon-first browser automation. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~1.9k | Automated safety check: Pass | MIT | 4 mo ago |
| 3 | 3.Check This skill should be used when the user wants to verify their changes before pushing, or update the project's rule checklists. | team-attention/ | 173 | — | ~1.8k | Automated safety check: Notes | MIT | 4 mo ago |
| 4 | 4.Compound This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. | team-attention/ | 173 | — | ~1.1k | Automated safety check: Notes | MIT | 4 mo ago |
| 5 | 5.QA Systematically QA test any application — web apps, native macOS apps, Electron apps, CLI tools, interactive REPLs, or anything on screen. | team-attention/ | 173 | — | ~2.6k | Automated safety check: Notes | MIT | 4 mo ago |
| 6 | This skill should be used when the user asks about "technical decision", "what to use", "A vs B", "comparison analysis", "library selection", "architecture decision", "which one to use"… | team-attention/ | 173 | — | ~1.4k | Automated safety check: Pass | MIT | 4 mo ago |
| 7 | Analyze an open-source project from What/Why perspective (not how-it's-implemented). | team-attention/ | 173 | — | ~2k | Automated safety check: Pass | MIT | 4 mo ago |
| 8 | 8.Dev Scan Collect diverse opinions on technical topics from developer communities. | team-attention/ | 173 | — | ~5k | Automated safety check: Pass | MIT | 4 mo ago |
| 9 | 9.Discuss "/discuss", "discuss this", "think with me", "is this a good idea?", "what do you think about", "problem definition", "explore this idea", "/discuss --scored", "interview me", "clarify… | team-attention/ | 173 | — | ~4.7k | Automated safety check: Pass | MIT | 4 mo ago |
| 10 | 10.Execute Plan-driven orchestrator. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~8.3k | Automated safety check: Notes | MIT | 4 mo ago |
| 11 | Google search via real Chrome browser (chromux). An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~1.3k | Automated safety check: Pass | MIT | 4 mo ago |
| 12 | 12.Issue GitHub issue creation skill. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~1.4k | Automated safety check: Pass | MIT | 4 mo ago |
| 13 | This skill should be used when the user asks to "find references", "참고할 만한 거", "similar implementation", "오픈소스 있나", "how others do this", "레퍼런스 찾아줘", or needs to find existing patterns (internal)… | team-attention/ | 173 | — | ~2.4k | Automated safety check: Pass | MIT | 4 mo ago |
| 14 | 14.Stepback One-shot perspective reset that surfaces blind spots mid-work. | team-attention/ | 173 | — | ~1.8k | Automated safety check: Pass | MIT | 4 mo ago |
| 15 | 15.Tribunal This skill should be used when the user says "/tribunal", "tribunal", "review this", "3-way review", "risk-value-feasibility check", or wants multi-perspective adversarial review. | team-attention/ | 173 | — | ~1.7k | Automated safety check: Notes | MIT | 4 mo ago |
| 16 | 16.Ultrawork This skill should be used when the user says "/ultrawork", "ultrawork", or wants to run the full specify → execute pipeline automatically with a single command. | team-attention/ | 173 | — | ~1.2k | Automated safety check: Notes | MIT | 4 mo ago |
| 17 | 17.Verify Run a full implementation verification pass after code or data changes. | team-attention/ | 173 | — | ~1.2k | Automated safety check: Pass | MIT | 4 mo ago |
| 18 | 18.Council This skill should be used when the user says "/council", "council", "deliberate", "multi-perspective decision", "트레이드오프 분석", "위원회 소집", "여러 관점으로 검토", or wants deep multi-perspective deliberation with… | team-attention/ | 173 | — | ~7k | Automated safety check: Notes | MIT | 4 mo ago |
| 19 | Deep web research skill using parallel subagents + chromux browser-explorer + Gemini. | team-attention/ | 173 | — | ~6k | Automated safety check: Pass | MIT | 4 mo ago |
| 20 | 20.Scaffold Greenfield project architecture + harness scaffolding for AI Agent productivity. | team-attention/ | 173 | — | ~6.9k | Automated safety check: Notes | MIT | 4 mo ago |
| 21 | 21.Bugfix Root cause based one-shot bug fix. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~4.8k | Automated safety check: Pass | MIT | 4 mo ago |
| 22 | 22.Clarify "/clarify", "clarify this", "keep asking until clear", "remove ambiguity", "clarify requirements", "clarify design", "clarify the plan", "질문 계속해", "모호한 게 없게", "명확해질 때까지", "계속 물어봐", "Q&A로 정리", "질문답변… | team-attention/ | 173 | — | ~1.9k | Automated safety check: Notes | MIT | 4 mo ago |
| 23 | 23.Mirror "/mirror", "mirror back", "echo back", "다시 설명해줘", "이해한 거 맞아?", "내가 뭘 원하는지 말해봐", "확인해줘", "paraphrase this", "너가 이해한 거 설명해봘", "what did I ask?" | team-attention/ | 173 | — | ~1.8k | Automated safety check: Pass | MIT | 4 mo ago |
| 24 | 24.Ralph Iterative task completion loop with Definition of Done verification. | team-attention/ | 173 | — | ~1.6k | Automated safety check: Notes | MIT | 4 mo ago |
| 25 | 25.Rulph Iterative rubric-based evaluation and self-improvement loop. | team-attention/ | 173 | — | ~4.3k | Automated safety check: Notes | MIT | 4 mo ago |
| 26 | Hoyeon execution workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~478 | Automated safety check: Pass | MIT | 4 mo ago |
| 27 | Hoyeon requirements workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~673 | Automated safety check: Pass | MIT | 4 mo ago |
| 28 | 28.Specify "/specify", "specify", "요구사항 정의", "requirements", "스펙 잡기", "뭘 만들어야 하는지", "기획 정리", "인터뷰해서 스펙" Turn a goal into structured requirements through systematic interview. | team-attention/ | 173 | — | ~7k | Automated safety check: Pass | MIT | 4 mo ago |
| 29 | Hoyeon blueprint workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~302 | Automated safety check: Pass | MIT | 4 mo ago |
| 30 | Hoyeon browser automation workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~252 | Automated safety check: Pass | MIT | 4 mo ago |
| 31 | Hoyeon ambiguity-resolution interview for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~342 | Automated safety check: Pass | MIT | 4 mo ago |
| 32 | Hoyeon deep research workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~267 | Automated safety check: Pass | MIT | 4 mo ago |
| 33 | Hoyeon developer community scan workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~247 | Automated safety check: Pass | MIT | 4 mo ago |
| 34 | Hoyeon Socratic discussion workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~458 | Automated safety check: Pass | MIT | 4 mo ago |
| 35 | Hoyeon Google/chromux search workflow for Codex. An agent skill from team-attention/hoyeon. | team-attention/ | 173 | — | ~241 | Automated safety check: Pass | MIT | 4 mo ago |
| 36 | Hoyeon implementation reference discovery workflow for Codex. | team-attention/ | 173 | — | ~270 | Automated safety check: Pass | MIT | 4 mo ago |