memo
Skill0 starsChanged 6 months agoApache-2.0View on GitHub
Quick memo to Obsidian Daily note
11 other projects use a version of this.
Adopted by
Most recently taken up by
- AIOSAI/AIPasstheir own version, first seen Nov 1, 2026
- jagoff/memotheir own version, first seen Nov 1, 2026
- kpatdev/my-skillstheir own version, first seen Oct 26, 2026
- nhhthong/cliotheir own version, first seen Oct 12, 2026
- gregmos/memoforgetheir own version, first seen Sep 24, 2026
- kpatdev/skillstheir own version, first seen Aug 8, 2026
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- anthropics/claude-for-legal★ 9.5ksame name
- AIOSAI/AIPass★ 312same name
- gregmos/memoforge★ 38same name
- jagoff/memo★ 25same name
- raphaelDkhn/worldbuilder★ 3same name
- nhhthong/clio★ 2same name
- Shawyeok/skills★ 1same name
- kpatdev/my-skills★ 0same name
- kpatdev/skills★ 0same name
- mhmarkhoffmann-lob/claude-desk★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- add-mesh-peerSkill
- adrSkill
- analyze-logsSkill
- codex-consultSkill
- codex-reviewSkill
- config-analyzerSkill
- cross-reviewSkill
- drawioSkill
- empirical-prompt-tuningSkill
- git-historySkill
- github-writingSkill
- hard-task-playbookSkill
- inherit-wipSkill
- interviewSkill
- ja-natural-reviewSkill
- mcp-smoke-via-claude-pSkill
- meeting-minutesSkill
- nerfstudio-trainerSkill
- obsidian-work-loggerSkill
- plan-with-qaSkill
- poll-sonnet-workersSkill
- post-merge-cleanupSkill
- release-applySkill
- ros2-inspectorSkill
- ros2-launch-debugSkill
- ros-analyzeSkill
- safe-pathspec-commitSkill
- setup-claude-localSkill
- split-advisorSkill
- surveySkill
- work-logSkill
- write-specSkill
- zenn-interviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read config.json to get output path
- Very specific: line 13
Create directory and file if they don't exist (mkdir -p + touch)
- Very specific: line 14
Add timestamp heading (HH:MM format, obtained from date +%H:%M in Bash at execution time)
- Very specific: line 52
allowed-tools は
Bash, Read: Write ツールは使わない。追記は上の quoted heredoc で
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
First, read ~/work/claude-skills/config.json to get the obsidian_daily_path.
Then append the following memo to {obsidian_daily_path}/$(date +%Y-%m-%d).md
Steps
- Read config.json to get output path
- Create directory and file if they don't exist (
mkdir -p+touch) - Add timestamp heading (HH:MM format, obtained from
date +%H:%Min Bash at execution time) - Append to end of file
Append rules
時刻の事前解決(重要)
quoted heredoc (<<'EOF') はシェル展開を全て抑止するので、本文中に $(date +%H:%M) や $TIME を書いても展開されない。時刻は先に Bash で date +%H:%M を実行して結果文字列を取得し、heredoc 本文にはその結果をリテラルで埋め込むこと。以下の2段階で実装する:
- Bash で
date +%H:%Mを実行(例: 結果が18:42) - 次に書き込むコマンドの heredoc 本文に
18:42を直接タイプする(変数ではなくリテラルとして)
エスケープ
$ARGUMENTS はバッククォート・$・引用符などを含みうる。必ず quoted heredoc で書き込むこと。echo や unquoted heredoc はシェル展開されて内容が壊れる。
書き込みコマンド例
時刻取得結果が 18:42、$ARGUMENTS が 明日MTGをレビュー の場合:
FILE=/path/to/2026-04-21.md
# 既存ファイルが有る場合のみ、既存最終行と新見出しの間を空行1行で区切る
# - ファイルが空なら何もしない(新規書き込みで冒頭に空行を作らない)
# - 末尾が LF 終端でないなら LF を 1 つ足して段落区切りを確保
if [ -s "$FILE" ]; then
[ "$(tail -c1 "$FILE" | wc -l)" -eq 0 ] && printf '\n' >> "$FILE"
printf '\n' >> "$FILE"
fi
cat >> "$FILE" <<'EOF'
## 18:42
明日MTGをレビュー
EOF(## 18:42 と本文は 実行時にリテラルで差し替える。変数は使わない。heredoc 冒頭に空行は入れない — 既存ファイルがある場合の空行は上の if ブロックで先に担保する)
その他
- 既存ファイルへの追記: 既存最終行と新
## HH:MM見出しの間に空行 1 行を入れる(上のifブロックで、LF 終端担保 + 空行 1 行の 2 段階で処理) - 新規ファイル: 冒頭にファイルレベル見出し(
# 2026-04-21など)は付けない。日付はファイル名に入っている。冒頭空行も作らない(上のifブロックが空ファイルをスキップするため自動的に担保される) - allowed-tools は
Bash, Read: Write ツールは使わない。追記は上の quoted heredoc で
Memo content
$ARGUMENTS
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

