← all publishers

rlaope

@rlaope source repo

Report this profile Claim this profile

• 313 skills
• 0 followers
• last month last updated

1. ▌
   Omh Support Operations 3 · rlaope

   [omh] Turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
   0 installs
2. ▌
   Omh Product Brief 2 · rlaope

   [omh] Turn product evidence into a decision-ready PRD, prioritization frame, and roadmap brief. Use when the user says: product requirements document, PRD, roadmap prioritization, 제품 요구사항 문서, 제품 기획서, 로드맵 우선순위.
   4 installs
3. ▌
   Omh Refactor Plan 2 · rlaope bundle

   [omh] Hermes refactor planning workflow: turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.
   0 installs
4. ▌
   Omh Rules Distill 2 · rlaope

   [omh] Hermes Rules Distill workflow: extract repeated principles from skills, prompts, traces, reviews, and failures into reviewed rule candidates without auto-mutating guidance. Use when the user says: rules-distill, rules distill, distill rules, rule distillation, principle distill, skill principles, extract agent rules, turn traces into rules.
   2 installs
5. ▌
   Context Memory Hygiene · rlaope bundle

   Invoke when deciding what to load into context, what to persist across turns or sessions, and what to drop — reads only what the task needs, writes durable handoffs, avoids context pollution, and chooses when to re-derive versus recall.
   0 installs
6. ▌
   Delegation Parallelism · rlaope bundle

   Invoke when deciding whether to split work across parallel agents/sessions or do it inline — tests scope independence, weighs coordination cost against the parallelism win, and sets an observation cadence for delegated work.
   0 installs
7. ▌
   Verification Discipline · rlaope bundle

   Invoke before claiming any task is done — defines what counts as evidence of completion (execution, not inspection) and how to verify at the layer the requirement actually lives at.
   0 installs
8. ▌
   Failure Mode Enumeration · rlaope bundle

   Systematically enumerate how code can break — boundaries, concurrency, partial failure, malicious input, time, resource exhaustion — before writing defenses, then convert the list into tests and guards while pruning paranoia that does not pay rent.
   0 installs
9. ▌
   State Probing · rlaope bundle

   Invoke before acting on any assumption about the runtime or environment — versions, running processes, file/disk reality, git state, network reachability. Grounds claims about the world in a cheap probe instead of a guess, and re-probes when state may have gone stale.
   1 install
10. ▌
    Honest Reporting · rlaope bundle

    Invoke when writing any status, completion, or result report — calibrates claims to the evidence actually gathered, marks the unmeasured as open, reports failures plainly, and distinguishes "verified at layer X" from "should work".
    0 installs
11. ▌
    Incremental Safety · rlaope bundle

    Decompose a large or risky change into a sequence of independently safe intermediate states, so the system stays green at every step and any step can be reverted alone.
    0 installs
12. ▌
    Exploration Strategy · rlaope bundle

    Build an accurate mental model of an unfamiliar codebase or problem before making any edit — structural scan, entry-point location, one end-to-end trace, and an explicit known-vs-assumed ledger.
    0 installs
13. ▌
    Self Correction Loop · rlaope bundle

    Invoke when an implementation attempt produces a failure signal (test failure, compile error, wrong output, crash, perf regression) and you must decide whether to retry, rethink, or back out — instead of hammering the same fix.
    0 installs
14. ▌
    Hypothesis Management · rlaope bundle

    Debug by maintaining 2-4 competing hypotheses with explicit evidence and kill criteria, choosing each probe to maximally discriminate between them instead of confirming a favorite.
    0 installs
15. ▌
    Spec To Code Fidelity · rlaope bundle

    Invoke when implementing from an authoritative written source — an RFC, academic paper, binary format spec, protocol document, or mathematical derivation — where correctness means matching the document, not just passing ad-hoc tests.
    0 installs
16. ▌
    Tradeoff Articulation · rlaope bundle

    Invoke when a design decision has multiple viable implementations and the choice affects performance, memory, complexity, or blast radius — forces enumerating real alternatives, quantifying the axes that matter, and recording what would reverse the decision.
    0 installs
17. ▌
    Ulw QA 2 · rlaope

    [omh] Hermes UltraQA workflow: adversarial QA and fix loops. Use when the user says: ultraqa, adversarial qa, hostile scenarios, e2e qa, real-world qa, qa scenario, release qa, 敵対的QA.
    1 install
18. ▌
    Ulw Loop 2 · rlaope bundle

    [omh] Hermes Loop workflow: agentic interviewer -> planner -> researcher -> builder -> reviewer cycles until a real gate. Use when the user says: loop, goal loop, long horizon goal, never stop, research plan goal feedback, token exhaustion resume, permission profile, star 10k.
    0 installs
19. ▌
    Ulw Perf 2 · rlaope

    [omh] Ultraperf - find where a system is actually slow, leaking, or expensive across runtime, memory, token cost, storage, rendering, inference, CI, and query domains, then fix one measured hot path at a time behind a regression budget. Use when the user says: ultraperf, ulw-perf, performance audit, performance bottleneck, find the bottleneck, profile the hot path, memory leak investigation, token cost hotspot.
    0 installs
20. ▌
    Ulw Work 2 · rlaope bundle

    [omh] Ultrawork - split an accepted plan into disjoint parallel lanes with per-lane acceptance criteria, verification commands, and owners; prevents two lanes editing the same file. Aliases: ulw. Use when the user says: ultrawork, parallel work, parallel implementation, parallel then integrate, high throughput, coding team, coordinated workers, finish until done.
    0 installs
21. ▌
    Omh Decide 2 · rlaope bundle

    [omh] Decide between options: tradeoffs, a recommendation, and a decision note you can act on. Use when the user says: strategy-brief, strategy brief, strategy memo, product strategy, strategic options, decision note, leadership strategy, next strategy.
    0 installs
22. ▌
    Ulw Context 2 · rlaope bundle

    [omh] Project terminology alignment workflow: look up, capture, correct, and align the words a repository uses before planning or handoff. Use when the user says: ulw-context, project terminology alignment, review project terms, align project terminology, terminology this project uses.
    0 installs
23. ▌
    Ulw Research 2 · rlaope bundle

    [omh] Deep research engine - grounding for specs and decisions: study open-source reference implementations with pinned refs, gather live web evidence with citation discipline, verify contested claims, and distill a decision-grounding dossier that planning consumes; for a decision brief use research-brief, for upstream guidance use best-practice-research. Use when the user says: research plan, literature review, research literature, review recent papers, deep research, deep-research, exhaustive research, saturation research.
    0 installs
24. ▌
    Omh Jit Learn 2 · rlaope

    [omh] Just-in-time learning workflow: select and confirm an immediate learning target, research credible sources, and prepare an application-first brief without popularity ranking. Use when the user says: jit-learn, learn next, learn now, blocker-specific learning target, highest-leverage learning target, immediate learning payoff, immediately applicable learning brief, source-backed learning brief.
    0 installs
25. ▌
    Omh Memory New 2 · rlaope

    [omh] Capture one bounded durable project or product memory candidate through explicit remember, refuse, or defer review; for existing Hermes memory use omh-memory-sync, and for a past decision use decision-recall. Use when the user says: memory-new, new memory, project memory, product memory, remember this project, remember this product, do not save, do not save this token.
    1 install
26. ▌
    Omh Ops Review 2 · rlaope

    [omh] Hermes Ops Review workflow: status, risks, blockers, priorities, and follow-ups. Use when the user says: ops-review, ops review, weekly ops review, status review, operating review, release risks, risks and blockers, priorities.
    0 installs
27. ▌
    Omh People Ops 2 · rlaope

    [omh] Turn hiring and people context into a fair, structured recruiting or people-operations brief. Use when the user says: recruiting plan, hiring scorecard, interview scorecard, candidate debrief, 채용 계획, 면접 평가표, 후보자 비교.
    0 installs
28. ▌
    Omh Image Cards 2 · rlaope

    [omh] Image prompt cards - turn meetings, reports, PRs, issues, research, and releases into domain-aware image prompt cards. Use when the user says: img-summary, img summary, visual prompt card, image card, image generation, image edit, edit this image, remove the background.
    0 installs
29. ▌
    Omh Media Input 2 · rlaope

    [omh] User-sent media - audio, video, YouTube links, screenshots, receipts, OCR, meeting recordings, transcripts, timestamps, and clip summaries, gated for source, permission, and hallucination risk. Use when the user says: media-input-operator, media input operator, media input, audio transcription, audio transcript, transcribe audio, transcribe this audio, meeting recording.
    0 installs
30. ▌
    Omh Voice Input 2 · rlaope

    [omh] Terse voice and mobile-style requests - turn short spoken-style asks into clarify, plan, status, handoff, or confirmation actions. Use when the user says: voice-operator, voice operator, voice-first, voice command, mobile command, short command, dictated command, dictated request.
    2 installs
31. ▌
    Omh Web Research 2 · rlaope

    [omh] Web lookup lane - settle a current-facts question in one cited retrieval round with retrieval dates and source-quality notes; for pre-spec grounding across reference implementations use `research`. Use when the user says: web-research, web research, web search, search the web, internet search, look up, look up sources, latest sources.
    0 installs
32. ▌
    Omh Data Analysis 2 · rlaope

    [omh] Hermes data analysis workflow: scope supplied data with provenance, causal-claim, and hallucination guards. Use when the user says: data-analysis, data analysis, dataset analysis, csv analysis, json analysis, log analysis, table analysis, analyze csv.
    2 installs
33. ▌
    Omh Meeting Brief 2 · rlaope

    [omh] Hermes Meeting Brief workflow: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.
    0 installs
34. ▌
    Omh Source Finder 2 · rlaope

    [omh] Source candidate inventory - prepare typed source candidates and acquisition status before downstream work; use ulw-research to fetch and cite them, or research-brief to turn them into a decision-ready brief. Use when the user says: source-finder, source finder, source acquisition, source intake, find papers and datasets, find datasets and repos, find papers, find arxiv link.
    0 installs
35. ▌
    Omh Paper Learning 2 · rlaope

    [omh] Hermes Paper Learning workflow: explain a supplied paper or paper/PDF at a selected level while preserving full section coverage and source evidence boundaries. Use when the user says: paper-learning, paper learning, paper-explainer, paper explainer, paper explanation, explain this paper, explain this arxiv paper, paper walkthrough.
    0 installs
36. ▌
    Omh Research Brief 2 · rlaope

    [omh] Business research brief - turns a market, competitor, pricing, or customer question into a structured evidence-vs-inference brief; for raw link gathering use ulw-research, and for ongoing multi-role research use research-department. Use when the user says: research-brief, business-research, business research, research brief, decision brief, pricing decision brief, decision-ready brief, source-backed business research.
    0 installs
37. ▌
    Omh Feedback Triage 2 · rlaope

    [omh] Hermes Feedback Triage workflow: cluster customer signals and choose the next workflow. Use when the user says: feedback-triage, customer-feedback-triage, feedback triage, customer feedback, feedback cluster, bug or feature, feature request triage, payment failure feedback.
    0 installs
38. ▌
    Omh Long Document Reading · rlaope bundle

    [omh] Long document reading workflow: read a very large PDF, contract, manual, or report through Hermes in page-anchored ranges with a coverage ledger. Use when the user says: long-document-reading, long document reading, summarize this pdf, read this pdf, process this pdf, go through this pdf, summarize this document, read this document.
    1 install
39. ▌
    Omh Finance Analysis 2 · rlaope bundle

    [omh] Turn finance and accounting inputs into a decision-ready variance, cash, and close-risk brief. Use when the user says: finance analysis, budget variance, budget vs actual, month-end close, 재무 분석, 예산 대비 실적, 월마감.
    0 installs
40. ▌
    Omh Operating Rhythm 2 · rlaope

    [omh] Hermes Operating Rhythm workflow: meeting minutes, scrum/sprint records, retros, decisions, and follow-up history. Use when the user says: operating-rhythm, operating rhythm, meeting minutes, meeting history, scrum record, sprint planning, sprint review, sprint retrospective.
    1 install
41. ▌
    Omh Autoresearch Goal 2 · rlaope

    [omh] Hermes adaptation for durable research-goal execution. Use when the user says: autoresearch-goal, research goal, durable research, critic research.
    0 installs
42. ▌
    Omh Curriculum Design 2 · rlaope bundle

    [omh] Turn a learning goal into a teachable curriculum, assessment plan, and learner-ready sequence. Use when the user says: curriculum design, learning objectives, assessment plan, 커리큘럼 설계, 학습 목표, 평가 계획.
    0 installs
43. ▌
    Omh Inference Serving 2 · rlaope bundle

    [omh] OMH Inference Serving workflow: choose the serving engine and quantization from decision tables, prepare deployment as an idempotent runbook with observed-only verification, and measure the endpoint with the standard TTFT/TPOT/goodput protocol. Use when the user says: inference-serving, inference serving, serve this model, serve the model, model serving, serving endpoint, vllm, llama.cpp.
    0 installs
44. ▌
    Omh Sales Development 2 · rlaope bundle

    [omh] Turn an account or market opportunity into a focused discovery, qualification, and next-step brief. Use when the user says: sales discovery, account plan, outbound messaging, 영업 발굴, 고객사 계획, 아웃바운드 메시지.
    0 installs
45. ▌
    Omh Reliability Review 2 · rlaope

    [omh] Hermes Reliability Review workflow: postmortems, SLOs, error budgets, incident follow-ups, and service reliability evidence. Use when the user says: reliability-review, reliability review, incident review, incident postmortem, postmortem, post-mortem, slo review, slo.
    0 installs
46. ▌
    Omh Support Operations 2 · rlaope

    [omh] Turn a support case into a clear customer reply, severity path, and owned next step. Use when the user says: support escalation, customer support reply, ticket triage, 고객 지원 에스컬레이션, 고객 답변 초안, 지원 티켓 분류.
    0 installs
47. ▌
    Omh Harness Session Inventory · rlaope

    [omh] Hermes harness session inventory workflow: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory.
    0 installs
48. ▌
    Omh Context Budget Review 2 · rlaope bundle

    [omh] Hermes Context Budget Review workflow: plan compact context, token/cost budgets, summarization checkpoints, and overflow recovery before long agent work. Use when the user says: context-budget-review, context budget review, context budget, token budget review, token budget, prompt budget, prompt caching, prompt cache.
    0 installs
49. ▌
    Omh Best Practice Research 2 · rlaope

    [omh] Hermes adaptation for bounded official/upstream best-practice research. Use when the user says: best-practice-research, best practice, official docs, upstream guidance, what do the docs say, check the docs.
    0 installs
50. ▌
    Omh External Connector Readiness · rlaope

    [omh] External connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
    0 installs
51. ▌
    Omh Legal Compliance Review 2 · rlaope bundle

    [omh] Surface contract and compliance risks, questions, and escalation points before a legal decision or action. Use when the user says: contract review, contract liability clause, regulatory analysis, compliance review, 계약서 검토, 규제 분석, 컴플라이언스 검토.
    1 install
52. ▌
    Omh Harness Session Inventory 2 · rlaope

    [omh] Hermes harness session inventory workflow: normalize Codex, Claude Code, Hermes, OpenCode, Cursor, MCP host, worktree, and wrapper session metadata into one drift-aware inventory. Use when the user says: harness-session-inventory, harness session inventory, session inventory, session adapter, session adapters, harness sessions, mcp inventory, mcp config inventory.
    1 install
53. ▌
    Omh Physical Device Readiness · rlaope

    [omh] Physical device readiness - gate robots, 3D printers, IoT relays, sensors, and lab hardware before trials; use external-connector-readiness for provider or connector adoption and toolbelt-readiness for missing control tools. Use when the user says: physical-device-readiness, physical device readiness, device safety readiness, physical device safety, hardware safety gate, 3d printer readiness, 3D printer safety, snapmaker printer safety.
    0 installs
54. ▌
    Omh External Connector Readiness 2 · rlaope

    [omh] External connector readiness - assess whether a named plugin, connector, API, data provider, or multimodal route is safe, affordable, fresh, and observable; use executor-runtime-readiness for coding-owner choice and toolbelt-readiness for missing capability inventory. Use when the user says: external-connector-readiness, external connector readiness, connector readiness matrix, plugin readiness matrix, provider readiness, api readiness, connector adoption, external plugin adoption.
    0 installs
55. ▌
    Omh Product Discovery Validation · rlaope bundle

    [omh] Test whether a customer problem, segment, and business hypothesis deserve product investment, ending in kill, pivot, persevere, or inconclusive before any PRD. Use when the user says: product-discovery-validation, product discovery validation, product discovery, customer discovery, customer discovery plan, zero to one validation, validate the problem before building, problem solution interview.
    0 installs
56. ▌
    Docs Sync · rlaope

    Audit and update Argus user-facing docs (README, docs/**/*.md, site/*.html) against the code truth. Detects version drift, command-count drift, i18n parity violations, and stale CLI examples. Use before a release, or any time the user asks to "sync docs", "update docs", "fix docs drift", "verify docs".
    2 installs
57. ▌
    Argus Jvm Harness · rlaope

    Continuous JVM monitoring + optimization + troubleshooting harness on top of the Argus CLI. Use when the user wants to watch a running JVM for trouble (GC regression, heap leak, thread growth, pause-time spikes) over a window of time and get a single severity-ranked report with recommended JVM flags. Bootstraps the Argus CLI via the official installer when it is not already on PATH.
    0 installs
58. ▌
    Release Sync · rlaope

    Audit and update Argus external distribution surfaces (Spring Boot starter, Helm chart, Docker, install scripts, Homebrew Formula, SDKMAN, GitHub Actions, action.yml) against gradle.properties and known-good upstream versions. Detects version drift, floating image tags, deprecated K8s APIs, and outdated dependencies. Use before a release, or when the user asks to "sync release", "update distributions", "check outdated deps", "verify external integrations".
    0 installs
59. ▌
    Karpathy Guidelines · rlaope

    Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code in this repo to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
    0 installs
60. ▌
    En · rlaope

    Aura-field auto-routing — read an incoming request's problem shape and engage the right nen abilities, stacked in dependency order when the work spans more than one discipline. Use when the user says "nen", "use nen", "nen mode", "run this through nen", "which skill applies", or "route this"; when a request plausibly spans more than one nen discipline; when you are about to pick a single skill and are not certain it is the right one; or when the user has asked for nen to be the standing baseline for the session.
    1 install
61. ▌
    Vow · rlaope

    Pre-commitment engineering — declare falsifiable vows before the work starts and audit every one before claiming done, discipline pledges distilled from the engaged skills' Done means plus scope pledges bounding the blast radius. Use when the user says "don't touch anything else", "only this file", "stay in scope", "no new dependencies", "don't tell me it's done until", "commit to your constraints", or "show me the failing test first"; when a previous attempt was declared done and was not; when a diff wandered into files nobody asked about; when en announces an engagement (the announcement is the vow moment); or when delegated work needs acceptance criteria the delegate can be audited against.
    0 installs
62. ▌
    Hatsu · rlaope

    Skill forging — distilling a team's recurring, hard-won practice into a new installable SKILL.md that meets the nen contract. Use when the user says "write a skill", "create a skill for", "turn this workflow into a skill", "codify our process", or "SKILL.md"; when someone says "we keep solving this the same way" or "the team keeps re-teaching this in review"; after a retro where the same lesson surfaces for the second or third time; or when an agent keeps making a mistake that a written discipline would have prevented.
    0 installs
63. ▌
    Emitter · rlaope

    Launch, positioning, and promotion — making finished work land with the audience that should care. Use when the user says "launch", "announce", "release notes", "changelog", "blog post", "tweet thread", "X thread", "Show HN", "Hacker News post", "how do I promote this", "who would care about this", or "positioning"; when a README needs a pitch instead of a manual; when something is built and working but nobody outside the repo knows it exists; or when launch copy already exists but reads like a feature list.
    0 installs
64. ▌
    Conjurer · rlaope

    Failure-mode-driven reliability engineering — enumerate how it breaks, give every mode a verdict, prove every handler with a reproducing test. Use when the user says "flaky", "harden this before launch", "what if this fails", "error handling", "timeout", "retry", "idempotency", or "race condition"; when an incident or postmortem lands; when a job crashes halfway and leaves partial state; when a webhook or queue consumer double-fires, sees double delivery, or charges a customer twice; when crash recovery is undefined; or when code is about to ship with only happy-path tests.
    0 installs
65. ▌
    Enhancer · rlaope

    Profiling-first performance engineering — baseline, profile, change one thing, re-measure. Use when the user says "slow", "make this faster", "optimize", "profile", "benchmark", or "hot path"; when they report latency problems, p99 spikes, low throughput, memory growth, or N+1 queries; when a request times out under load but works in dev; when someone wants to know why an endpoint takes 800ms; or when a perf change is proposed without a number attached.
    1 install
66. ▌
    Specialist · rlaope

    Reverse engineering and mechanism-comparison research — when the docs run out, read the artifact itself and prove how the thing actually works. Use when the user asks "how does <tool> actually do it", says "reverse engineer this", "undocumented behavior", "the docs don't match what happens", or "the docs never mention it"; when a dependency, vendor SDK, legacy system, or external API behaves in ways nobody on the team can explain; when the ask is to compare implementations of the same mechanism across libraries or competitors; when someone says "we've tried everything" about a black-box system; or when the only source of truth is minified bundles, compiled binaries, or network traffic.
    0 installs
67. ▌
    Transmuter · rlaope

    Behavior-preserving refactoring under characterization tests, plus severity-rated code review. Use when the user says "refactor", "clean up", "tech debt", "code review", "extract", "rename", "restructure", "this file is a mess", or "impossible to modify"; when every small change breaks something unrelated; when cleanup has to land before the next feature has anywhere to go; when code is called hard to change, scary to touch, or too tangled to test; when requirements shifted and the current shape fights the new feature; when a PR needs review for structure and maintainability; or when every small change keeps ballooning because everything touches everything.
    0 installs
68. ▌
    Manipulator · rlaope

    Orchestration engineering for multi-agent and deep-research work — decomposition, routing, prompt design, and verified delegation. Use when the user says "plan this", "break this down", "delegate", "orchestrate", "subagent", "task distribution", "parallel workstreams", "split this across agents", "hand this to three agents", "write a prompt for", or "research X thoroughly"; when work must be divided into workstreams that different agents or people can own; when they ask which model or agent should handle something; when work is multi-step and ambiguous enough that one agent charging ahead would guess wrong; when several independent investigations could run in parallel; or when a subagent has reported "done" and someone is about to believe it.
    2 installs
69. ▌
    Docs · rlaope

    Sync all documentation (README, docs/, CLAUDE.md) with current codebase state
    0 installs
70. ▌
    Plan · rlaope

    Analyze task scope and recommend a bestwork team composition before executing
    4 installs
71. ▌
    Trio · rlaope

    Execute tasks in parallel with dynamically assigned agents per task
    0 installs
72. ▌
    Blitz · rlaope

    Maximum parallelism burst — all tasks execute simultaneously with no coordination overhead
    0 installs
73. ▌
    Trace · rlaope

    Evidence-driven causal tracing — competing hypotheses, falsification, rebuttal round, recommended next probes
    1 install
74. ▌
    Agents · rlaope

    List all bestwork specialist agent profiles
    2 installs
75. ▌
    Doctor · rlaope

    Diagnose the current project's deploy config vs actual code — find mismatches between what's configured and what exists
    0 installs
76. ▌
    Health · rlaope

    Quick session health check
    0 installs
77. ▌
    Review · rlaope

    Check code for hallucinations and platform mismatches
    2 installs
78. ▌
    Status · rlaope

    Show current bestwork-agent configuration
    0 installs
79. ▌
    Update · rlaope

    Check for updates and upgrade bestwork-agent — plugin cache + hooks + HUD all at once
    2 installs
80. ▌
    Clarify · rlaope

    Ask targeted clarifying questions to uncover missed requirements before execution
    2 installs
81. ▌
    Deliver · rlaope

    Persistent completion mode — tasks must finish fully with verify/fix loops until done
    2 installs
82. ▌
    Install · rlaope

    Install bestwork hooks into Claude Code
    4 installs
83. ▌
    Onboard · rlaope

    First-time setup guide and feature walkthrough
    0 installs
84. ▌
    Delegate · rlaope

    Autonomous execution — classify, allocate, and execute without confirmation
    0 installs
85. ▌
    Meetings · rlaope

    Search and browse past meeting logs
    0 installs
86. ▌
    Sessions · rlaope

    List Claude Code sessions with stats
    1 install
87. ▌
    Validate · rlaope

    Feature validation gate — research, define purpose, stress-test from real user perspective before building
    0 installs
88. ▌
    Changelog · rlaope

    Auto-generate changelog from git history
    0 installs
89. ▌
    Waterfall · rlaope

    Sequential staged processing — each stage must pass before the next begins
    0 installs
90. ▌
    Pipeline Run · rlaope

    Queue and auto-process multiple GitHub issues — each gets its own branch, team, PR, and merge
    0 installs
91. ▌
    Superthinking · rlaope

    1000-iteration thought simulation — plan, build, validate, critique, amplify
    1 install
92. ▌
    Codework · rlaope bundle

    Run the recurring repo delivery loop: choose or clarify the next goal, run the real ralplan gate, implement through ultragoal or ultrawork, open a PR, run code review, wait for CI/DCO, fix failures, then ask for human-in-the-loop merge approval before merging and syncing. Use when the user says codework, asks for the next implementation cycle, or wants planning-to-PR automation with explicit HITL before merge.
    2 installs
93. ▌
    Omh Memory New · rlaope

    [omh] Capture one bounded durable project or product memory candidate through explicit remember, refuse, or defer review; for existing Hermes memory use omh-memory-sync, and for a past decision use decision-recall. Use when the user says: memory-new, new memory, project memory, product memory, remember this project, remember this product, do not save, do not save this token.
    9 installs
94. ▌
    Omh Ops Review · rlaope

    [omh] Hermes Ops Review workflow: status, risks, blockers, priorities, and follow-ups. Use when the user says: ops-review, ops review, weekly ops review, status review, operating review, release risks, risks and blockers, priorities.
    13 installs
95. ▌
    Omh People Ops · rlaope

    [omh] Turn hiring and people context into a fair, structured recruiting or people-operations brief. Use when the user says: recruiting plan, hiring scorecard, interview scorecard, candidate debrief, 채용 계획, 면접 평가표, 후보자 비교.
    13 installs
96. ▌
    Omh Live Info · rlaope

    [omh] Policy overlay for live lookups - add provider, freshness, units, and source-quality gates after preferring native live-data tools for ordinary weather, finance, sports, maps, and time-zone requests. Use when the user says: live-info-operator, live info operator, live information, real time information, real-time information, weather today, current weather, weather forecast.
    10 installs
97. ▌
    Omh Visual QA · rlaope bundle

    [omh] Hermes visual-qa workflow: prepare observed-only rendered QA gates for web, frontend, image, document, and TUI surfaces. Use when the user says: visual-qa, visual qa, visual QA, visual quality assurance, visual check, web qa, web visual qa, screenshot qa.
    10 installs
98. ▌
    Ulw Interview · rlaope

    [omh] Hermes Deep Interview workflow: one-question-at-a-time clarification. Use when the user says: deep-interview, interview, clarify, feature shaping, ambiguous product request, one question, 要件を詰めて, 曖昧な要求.
    11 installs
99. ▌
    Omh Cto Loop · rlaope

    [omh] Hermes CTO Loop workflow: roadmap, PM, technical tradeoffs, risk, delivery, release, and follow-up operating cadence. Use when the user says: cto-loop, cto loop, cto, cto pm, pm dev qa security ops, roadmap technical tradeoffs, technical tradeoff, delivery risk.
    8 installs
100. ▌
     Omh Frontend · rlaope bundle

     [omh] Hermes frontend workflow: prepare design-system-driven web and terminal (TUI) UI creation, redesign, polish, accessibility, performance, and visual QA handoffs. Use when the user says: frontend, front-end, front end, frontend skill, web ui, ui ux, landing page, web app layout.
     8 installs