achievements
starsforks
How to install achievements?
rlaope/oh-my-hermes/achievements
$npx -y skills add rlaope/oh-my-hermes --skill achievements[omh] Hermes achievements observation workflow: summarize hermes-achievements badges, tiers, recent unlocks, and progress from local plugin artifacts.
SKILL.md
| 1 | # Achievements |
| 2 | |
| 3 | This is a Hermes-native `achievements` workflow skill. |
| 4 | |
| 5 | ## Why This Exists |
| 6 | |
| 7 | `achievements` exists so Hermes users can ask for this workflow in chat and receive a structured, evidence-bounded OMH operating surface instead of ad hoc narration. |
| 8 | |
| 9 | ## Do Not Use When |
| 10 | |
| 11 | - The request is already handled by a narrower explicit skill with stronger evidence. |
| 12 | - The user asks OMH to secretly run external platforms, connectors, schedulers, file exports, or runtime agents. |
| 13 | - The only safe answer is to ask for missing authority, credentials, target, or observed evidence first. |
| 14 | |
| 15 | ## Examples |
| 16 | |
| 17 | Good example: |
| 18 | |
| 19 | - Prompt: achievements show my unlocked badges and what is closest to the next tier. |
| 20 | - Expected behavior: Produce `show_achievements_summary` with required context, wrapper actions, and not-evidence boundaries. |
| 21 | - Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution. |
| 22 | |
| 23 | Bad example: |
| 24 | |
| 25 | - Prompt: achievements recompute my session history and grant the missing badges. |
| 26 | - Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened. |
| 27 | - Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence. |
| 28 | |
| 29 | ## Completion Checklist |
| 30 | |
| 31 | - The run or workflow scope, metric window, failure modes, and cost/latency boundary are named. |
| 32 | - Local telemetry, provider truth, billing truth, and completion evidence are separate states. |
| 33 | - Warnings name the next measurement or operator review action. |
| 34 | |
| 35 | ## Recovery Notes |
| 36 | |
| 37 | - If provider metrics are unavailable, report only local metadata and mark provider truth not_observed. |
| 38 | - If cost or latency looks risky, surface a warning plus the next measurement rather than a completion claim. |
| 39 | |
| 40 | ## OMH Context Rail |
| 41 | |
| 42 | - This skill is part of OMH's Hermes workflow layer, not a standalone executor. |
| 43 | - Product context: OMH is a Hermes-native workflow pack: choose skills, shape work, prepare artifacts, show status, and hand off with evidence boundaries. |
| 44 | - Current lane: **Automation and status** (`achievements`, `workspace-audit`, `production-audit`, `automation-blueprint`, `github-event-ops`, `agent-board`, `gateway-intent-card`, `voice-operator`, `+26 more`) - schedules, status, health, and ops review. |
| 45 | - If the user intent belongs to another OMH lane, hand back to `oh-my-hermes` or name the adjacent workflow instead of force-fitting this skill. |
| 46 | - Cross-skill context: every OMH skill: match lane; generic tool can render or execute. |
| 47 | - Generic-tool checkpoint: image->img-summary; frontend->frontend/a11y/visual-qa; paper->paper-learning; content->content-operator; media->media-input-operator; file->materials-package; search->web-research; live->live-info-operator; audit->workspace/production/security; failures->build-failure; verify->verification-gate; code->codegraph/onboarding/ultraprocess. |
| 48 | - Coverage: Every generated workflow skill carries this rail. |
| 49 | - Normal users talk to Hermes; OMH CLI is infra. |
| 50 | - Boundary: Prepared OMH routing, cards, handoffs, or artifacts are not observed execution, image generation, delivery, review, CI, merge-readiness, or merge evidence. |
| 51 | |
| 52 | ## Use When |
| 53 | |
| 54 | Use when the user asks which achievements or badges they unlocked, badge progress or tiers, recent unlocks, or wants an achievements section prepared for a report. |
| 55 | |
| 56 | Strong routing signals: `achievements`, `achievement`, `badges`, `badge`, `my badges`, `show achievements`, `achievement summary`, `unlocked badges`, `badge progress`, `achievement tier`, `recent unlocks`, `badge share card`, `업적`, `배지`, `뱃지`, `도전과제`, `업적 요약`, `実績`, `バッジ`, `成就`, `徽章` |
| 57 | |
| 58 | ## Catalog Metadata |
| 59 | |
| 60 | Category: `observability` |
| 61 | Phase: `telemetry-card` |
| 62 | Hermes role: `tracker` |
| 63 | Quality tier: `workflow-surface-gated` |
| 64 | |
| 65 | Quality bar: |
| 66 | |
| 67 | - Name the user-facing workflow objective, required context, next action, and stop condition. |
| 68 | - Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence. |
| 69 | - Expose missing tools, credentials, targets, or observations as user-visible gaps. |
| 70 | |
| 71 | Handoff policy: |
| 72 | |
| 73 | Keep this as Hermes-facing orchestration guidance first. Prepare executor, connector, gateway, or host-runtime handoff only when the user accepts that next step and observed evidence can be recorded. |
| 74 | |
| 75 | Required inputs: |
| 76 | |
| 77 | - user request |
| 78 | - target context |
| 79 | - delivery or status expectation |
| 80 | - known missing evidence |
| 81 | |
| 82 | Expected outputs: |
| 83 | |
| 84 | - hermes_achievements_observation/v1 summary or badge list |
| 85 | - recent unlocks and progress hints |
| 86 | - next action |
| 87 | - prepared-vs-observed boundary |
| 88 | |
| 89 | Artifact expectations: |
| 90 | |
| 91 | - hermes_achievements_observation/v1 metadata-only payload fr |
People who liked this also viewed
6 picksType
- lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026
- lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026
- lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。 当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026
- lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026
- lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026
- lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026
