All authors
Claude Skills by JeongJaeSoon
github.com/JeongJaeSoon48 skills0 installs26 views
- Setup Agent GuardDiagnose, install, and verify Agent Guard's plugin-local binary, jq and gitleaks dependencies, the active host integration, and live hook protection. Use when Agent Guard reports degraded protection, a SessionStart warning asks for setup, plugin hooks fail or appear bypassed, or a user asks to finish or repair Agent Guard installation.Votes: 0GitHub stars: 39
- Setup ShellInstall or refresh Agent Guard's plugin-local shell integration. Use when the user explicitly asks to enable or update shell command masking, or when a shell-integration warning directs them to rerun setup-shell.Votes: 0GitHub stars: 39
- Setup Agent GuardDiagnose, install, and verify Agent Guard's plugin-local binary, jq and gitleaks dependencies, the active host integration, and live hook protection. Use when Agent Guard reports degraded protection, a SessionStart warning asks for setup, plugin hooks fail or appear bypassed, or a user asks to finish or repair Agent Guard installation.Votes: 0GitHub stars: 39
- Setup ShellInstall or refresh Agent Guard's plugin-local shell integration. Use when the user explicitly asks to enable or update shell command masking, or when a shell-integration warning directs them to rerun setup-shell.Votes: 0GitHub stars: 39
- ArchitectSketch types, signatures and module structure before code, then stay in the loop as it fills in. Use for /architect, 'design this', \"상세 설계안 작성해줘\", \"설계안 다듬어줘\", \"구현 계획 짜줘\", or non-trivial work.Votes: 0GitHub stars: 3
- ArenaSpawn N parallel candidates at the same task, pick a base, graft the strongest parts of the losers into it. Use for /arena, 'arena this', 'throw it in the arena', or when one attempt at a non-trivial artifact would lock in the wrong shape.Votes: 0GitHub stars: 3
- BriefStatus report: \"현황 보고해줘\", \"상태 보고해줘\", \"브리핑해줘\", \"진행 상황 알려줘\", \"진행상황 표로\", `/brief`, a turn ending in a report on several items. Stage table only: \"단계표 보여줘\", \"stage table\", `/agent-skills:stage`. To-dos and held queue only: \"할 일 보여줘\", \"보류 큐 보여줘\", \"to-do list\", `/agent-skills:todo`. \"어디까지 했지\" is recall.Votes: 0GitHub stars: 3
- Deliver TicketUse when working a ticket from first edit to done: a PR opened, updated or merged (\"PR 올려줘\", \"머지해줘\", \"머지까지 진행해줘\", \"머지되면 이어서\"), a release after it (\"릴리즈까지 진행해줘\"), \"리뷰 코멘트 대응해줘\", proof it works (\"동작확인하고 머지\", \"내가 확인할 거 있어?\"), \"이 티켓 끝내줘\", \"ship it\". An orchestrator dispatches it instead.Votes: 0GitHub stars: 3
- Dispatch CardUse to start a new Orca card: work for another repo or a side branch while this session goes on — \"별도 세션으로 진행해줘\", \"~ repo 에 작업 지시해줘\" — an orchestrator's change work, and the next ticket once this one is done — \"핸드오프\", \"다음 티켓 진행해줘\", \"남은 작업 있어?\", \"머지하고 다음 진행해줘\".Votes: 0GitHub stars: 3
- End SessionUse to end, close or archive this session, card or worktree — \"종료해줘\", \"세션 종료해줘\", \"현재 세션 정리해줘\", \"아카이브해줘\", \"머지하고 종료하자\", \"end this session\" — before an Orca worker's worker_done, or when a handoff or the brief says to close. Bare \"정리해줘\"/\"마무리해줘\" or \"작업 기록 남겨줘\" records and keeps the session.Votes: 0GitHub stars: 3
- Figure It OutDesign an auditable playbook before code for a large migration or multi-part change, or work reviewed after the human steps away — /figure-it-out, \"알아서 설계해서 진행해줘\", \"자리 비운 동안 끝내줘\". Parallel tickets on cards are orchestrate.Votes: 0GitHub stars: 3
- InterrogateUse for \"interrogate\", \"adversarial review\", \"multi-model review\", \"challenge this\", \"stress test this code\", \"find blind spots\", or \"tear this apart\". Multiple LLM reviewers challenge changes from independent angles.Votes: 0GitHub stars: 3
- OrchestrateUse when this session is the top-level orchestrator (\"오케스트레이터로\", \"모든 세션 관리해줘\", \"이 세션도 편입해줘\") or drives a program to done through Orca workers — \"PM 겸 오케스트레이터로 끝까지\", 3+ tickets in parallel, \"대시보드 갱신해줘\", \"resume\" another lead's program, or why its PRs are stuck.Votes: 0GitHub stars: 3
- PrinciplesUse when a design, refactor, verification or delegation call needs a named principle: diff size, where validation goes, proof, follow-up tickets, splitting work across agents.Votes: 0GitHub stars: 3
- Prune CommentsUse to cut comments in a diff to what the code cannot say: /prune-comments, \"주석 정리해줘\", and deliver-ticket's pre-review step. Docs and PR prose are write-plainly.Votes: 0GitHub stars: 3
- Reap ResourcesUse when the machine is slow or cluttered with what finished sessions and agents left behind — \"방치 리소스 정리해줘\", \"죽은 프로세스 정리\", \"메모리·CPU 누가 먹고 있어\", \"끝낸 orca 세션·worktree 정리해줘\", \"janitor\" — and for the resource steward's and janitor's rounds. Inventories first, reaps only listed targets, files go to the trash.Votes: 0GitHub stars: 3
- RebootUse first after this session, Orca or the machine restarted, or after a compaction — \"재시작했어\", \"재부팅했어\", \"Orca 재시작했어\", \"세션 다시 띄웠어\", \"복구 점검해줘\" — to restore the Run binding, inbox wait and workers' terminals. What the work was is recall.Votes: 0GitHub stars: 3
- RecallRebuild recent working context from past sessions, live state and the shared record into a short brief. Use for \"어디까지 했지\", \"이번 주에 뭐 했지\", 'catch me up', or resuming after a restart. Status of work in flight is brief. An orchestrator dispatches it instead.Votes: 0GitHub stars: 3
- ReflectLessons and skill edits from three reviewers, or how a run went. For reflect, \"스킬에 반영해줘\", \"스킬이 왜 안 떴어\", \"이 세션 돌아보고 스킬 개선해줘\", \"개선 이력 보여줘\", Close, flow-improver rounds; measure mode for \"성과 측정\", derived-ticket growth, backlog convergence, rework, escaped defects, tokens per merged PR. An orchestrator dispatches it instead.Votes: 0GitHub stars: 3
- Secure FillUse when a browser auth screen needs a secret the agent must not see — \"토큰 입력해줘\", \"비밀번호 칸 채워줘\", \"secure-fill\". The value goes from the Keychain to the page after the owner's Touch ID. Never read, echo or paste the secret, and never edit the allowlist.Votes: 0GitHub stars: 3
- Setup PcUse to install agent-skills on another PC or bring an installed PC up to date — \"새 PC 세팅해줘\", \"다른 PC 에서도 똑같이 쓰게 해줘\", \"agent-skills 설치 점검\", \"agent-skills 업데이트해줘\", \"플러그인 최신화\", \"update agent-skills\". Dry-run only; the human runs the one `--apply` line. One auto-mode denial is tune-automode.Votes: 0GitHub stars: 3
- Show Me Your WorkKeep a reviewable decision trail (what, why, evidence, result per decision) for long, unattended or multi-phase work. Use for /show-me-your-work or work a human reviews after stepping away.Votes: 0GitHub stars: 3
- Skills ConfigUse when the user wants a value in ~/.claude/agent-skills.json changed, or a permissions.allow rule added to or removed from their user settings.json — \"agent-skills 설정 바꿔줘\", \"prs.after_hours 켜줘\", \"allow 규칙 추가해줘\". Emits a script the user runs; never edits those files. autoMode rules start in tune-automode.Votes: 0GitHub stars: 3
- TddUse when fixing a bug that has a cheap local test target, or when the user asks for TDD, a failing test or a regression test. Skip when the test path is unclear, expensive or integration-heavy.Votes: 0GitHub stars: 3
- Tune AutomodeUse when auto mode denied an action and the user wants that kind allowed, or wants auto mode's rules changed — \"auto mode 가 막았어\", \"이거 허용되게 규칙 추가해줘\", \"autoMode 규칙 고쳐줘\". Drafts the smallest rule as a script the user runs; never edits settings.json. permissions.allow is skills-config.Votes: 0GitHub stars: 3
- Ui ReviewUse before a mockup, screen or UI PR is shown to a person, and after one points out a UI problem: measures layout and consistency and walks the flow — \"UI 리뷰해줘\", \"시안 점검해줘\", \"화면 밸런스 봐줘\", \"보여주기 전에 UI 확인해줘\". Screenshots for a PR are deliver-ticket's.Votes: 0GitHub stars: 3
- Use NotesUse whenever working docs are read or written — \"노트에 기록해줘\", \"노트에 남겨줘\", \"KB에 정리해줘\", \"설계안을 노트에\", design docs, worklogs, program notes, \"정본\", a note path. Routes to the configured notes store.Votes: 0GitHub stars: 3
- Use TrackerUse for any Linear or Jira ticket operation — read, search, label, comment, relate, move, \"티켓 갱신해줘\", \"update the ticket\" — or when a skill or script needs ticket data. What a new ticket says is write-ticket's.Votes: 0GitHub stars: 3
- Watch MentionsUse to pick up chat that concerns the user as work — \"멘션 감시\", \"나한테 온 슬랙 정리해줘\", \"내가 말한 스레드에 새 답글 있어?\", \"watch my mentions\" — and each watch-mentions round. Posting is slack-post; GitHub reviews are watch-prs.Votes: 0GitHub stars: 3
- Watch PrsUse to pick up PRs waiting on the user, or the user's PRs waiting on reviewers — \"리뷰 요청 온 PR 정리해줘\", \"내 PR 리뷰 리마인드\", \"머지 가능한 내 PR 머지해줘\", \"내가 승인해야 할 봇 PR\", \"watch my PRs\", \"GitHub 알림 오면 깨워줘\" — and each watch-prs automation round. A program's own PRs are orchestrate's.Votes: 0GitHub stars: 3
- Write PlainlyUse when drafting or revising durable prose — ticket, PR body, commit, doc, note, report, skill text — or fixing padded, translated or machine-written prose: \"문장 다듬어줘\", \"읽기 쉽게 고쳐줘\", \"AI 티 안 나게\", \"번역투 고쳐줘\", \"unslop\".Votes: 0GitHub stars: 3
- Write SkillUse before writing or changing a skill, agent definition or CLAUDE.md-style file, and before committing it — \"스킬 만들어줘\", \"스킬 고쳐줘\", \"write a skill\", reflect's Apply step.Votes: 0GitHub stars: 3
- Write TicketUse when asked to write or file a ticket or issue (\"티켓 만들어줘\", \"티켓 기표해줘\", \"이슈로 남겨줘\"), including a ticket request inside another question and follow-ups filed from a finding.Votes: 0GitHub stars: 3
- GradersNo description providedVotes: 0GitHub stars: 3
- GradersNo description providedVotes: 0GitHub stars: 3
- GradersNo description providedVotes: 0GitHub stars: 3
- ChallengeBlast radius: what a change could break beyond its diff, proven by running code; 'blast radius of X', \"이거 바꾸면 뭐가 깨져\", \"영향 범위 봐줘\", a small diff you don't trust. Interrogate: \"interrogate\", \"adversarial review\", \"challenge this\", \"find blind spots\" on a design, plan or decision. A PR headed to main is deliver-ticket's review.Votes: 0GitHub stars: 3
- Explain CodeBefore changing unread code: '이 구조 설명해줘', 'X는 어떻게 동작해', '이건 어디에 둬야 해', '왜 이렇게 됐어', '이 결정 배경이 뭐야', 'teach me this', '이거 제대로 이해하고 싶어', '이 변경 이해시켜줘', 'feature map 만들어줘', '기능 지도 그려줘', '지금 뭐가 구현돼 있는지 정리해줘'. Verify maps: verification-skill. An orchestrator dispatches it instead.Votes: 0GitHub stars: 3
- Fan OutFan out parallel workers. Sweep splits one question, returns one report: /swarm, \"병렬로 훑어줘\", \"나눠서 동시에 확인해줘\". Compete runs candidates at one task, picks a base, grafts in the rest: /arena, \"경쟁시켜줘\", \"여러 버전 만들어서 비교해줘\". Landing tickets is orchestrate.Votes: 0GitHub stars: 3
- Verification SkillA verify-* skill drives the app like a user. Create: /create-verification-skill, \"verify 스킬 만들어줘\", a reusable verification harness in scope. Maintain: \"verify 스킬 점검해줘\", the weekly round, a verify-* skill that failed to drive a feature. Checking one change is not this. An orchestrator dispatches it instead.Votes: 0GitHub stars: 3
- ArchitectSketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use for /architect, 'architect this', 'design this', or non-trivial work where jumping to code would lock in the wrong shape.Votes: 0GitHub stars: 3
- HowUse for \"how does X work\", code walkthroughs before changing something, and placement / ownership / layering questions (\"where should this live\", \"which package owns this\", \"is this the right layer\"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.Votes: 0GitHub stars: 3
- Principle Explain The NumberApply before you trust, report, or act on a number you measured: a speedup, a regression, a throughput, a latency, or an eval result. Find what limits it, and rule out that it measured something other than the work you think.Votes: 0GitHub stars: 3
- RecallReconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.Votes: 0GitHub stars: 3
- ReflectSpawn three parallel review subagents over the active transcript, surface learnings, and route each to a concrete edit on an existing skill. Use when the user says reflect.Votes: 0GitHub stars: 3
- Show Me Your WorkKeep a reviewable decision trail for long-running or unattended work: a TSV log with one row per decision (what, why, evidence, result). Local by default; commit it when a reviewer needs the trail to trust the result. Use for /show-me-your-work, autonomous or multi-phase runs, or work a human reviews after stepping away.Votes: 0GitHub stars: 3
- SwarmFan out N parallel workers, drain them, and return one report. Use for /swarm, 'swarm this', or parallel coverage, races, gauntlets, and exploration.Votes: 0GitHub stars: 3
- WhyUse for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.Votes: 0GitHub stars: 3