メニュー
Append a one-line learning to the local harny inbox. Fast, non-analytical capture — copies text verbatim, no analysis, no follow-ups. Use when the user wants to note something about harny adoption mid-conversation without breaking flow.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/lfnovo/harny --skill learnコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Analyze a Harny 0.5 run from run.json v4, audit events, normalized attempt transcripts, ChangeSets, and provider usage. Use after failed, retried, slow, costly, paused, mixed-provider, or otherwise surprising runs.
Walk a repo through the harny readiness checklist. Score 10 dimensions Red/Yellow/Green, surface anti-signals, output a scorecard + prep checklist. Use when adopting harny in a new repo, or troubleshooting why it struggles in a familiar one.
Onboard and route users through Harny's declarative Claude/Codex workflows, local run state, provider configuration, human review, PR delivery, inspection, and cleanup. Use when someone is new to Harny, asks how it works, or needs help choosing the right Harny skill or workflow.
| name | learn |
| description | Append a one-line learning to the local harny inbox. Fast, non-analytical capture — copies text verbatim, no analysis, no follow-ups. Use when the user wants to note something about harny adoption mid-conversation without breaking flow. |
| allowed-tools | Bash, Read, Write, Edit |
Fast, frictionless capture into the project's local harny inbox at <cwd>/.harny/LEARNINGS.local.md. Drained later by the drain skill.
The whole point is zero friction. The user is mid-conversation and wants to note something without breaking flow. Do not analyze. Do not ask follow-ups. Do not propose solutions. Capture and return.
Path: <cwd>/.harny/LEARNINGS.local.md. The cwd is the current working directory of the conversation.
If .harny/ does not exist, create it. The file .harny/.gitignore (containing * + !.gitignore) ships with harny runs and keeps everything inside .harny/ out of git, including this inbox. If .harny/ is being created here for the first time, also write that gitignore.
Use this header exactly:
# harny learnings inbox
Working memory, append-only, gitignored. Drain via `/drain`.
Entry format: `- [<ISO UTC timestamp> · <branch>] <text>`
2026-04-23T18:45:00Z. Use date -u +%Y-%m-%dT%H:%M:%SZ via Bash.git rev-parse --abbrev-ref HEAD. If the repo is detached or git errors, use -.Single-line format:
- [2026-04-23T18:45:00Z · main] the raw text verbatim
If the captured text has newlines, indent continuation lines with two spaces so the bullet list stays valid:
- [2026-04-23T18:45:00Z · main] first line
continuation
more continuation
Copy the user's text verbatim. Do not rewrite, do not summarize, do not "improve" the wording.
One short line back to the user, then return to whatever was being discussed:
Captured to
.harny/LEARNINGS.local.md. Back to what we were doing.
No questions. No analysis. No "would you like me to also...".
.harny/LEARNINGS.local.md and (on first creation) .harny/.gitignore.All of that belongs to the drain skill, invoked separately when the user is ready to triage accumulated entries.
args provided. Ask one short question: "What do you want me to capture?" — then return to the steps above. Do not ask for elaboration on the content.args starts with the word drain. Do not run capture. Tell the user this skill is for capture only and suggest /drain for triage. Do not invoke drain automatically..harny/ exists but is not a directory (e.g., a file with that name). Stop and report — do not overwrite.git command unavailable. Use - for the branch field rather than failing.