x-account-enrichment
Enrich skeleton X/Twitter account entity pages to full quality (8-15KB), matching antirez-com.md / simon-willison.md depth.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Enrich skeleton X/Twitter account entity pages to full quality (8-15KB), matching antirez-com.md / simon-willison.md depth.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Comprehensive wiki health checking, maintenance, and remediation — duplicate detection, entity dedup/disambiguation, link auditing/fixing, page splitting, source-linking lint, wikilink remediation, tag taxonomy audit and normalization, pre-commit enforcement, language enforcement (JP→EN bulk translation, detection regex, cron-assisted migration), and decision-matrix-driven cleanup.
Comprehensive wiki maintenance: daily structural health checks (index reconciliation, log separator fixes, pipeline watchdog alerts), comparison page updates (adding items to multi-section comparison tables), and page relocation (moving/renaming pages while maintaining link integrity).
Pre-flight checklist and procedures for archiving, deleting, or migrating Hermes skills. Prevents accidental removal of cron-referenced skills. Covers the 3-layer skill structure and config.yaml management. Includes skill inventory management, promotion workflows, and archival conventions.
Karpathy's LLM Wiki: build/query interlinked markdown KB.
Deep analysis of blog authors' recent thoughts, philosophy, and positions. Goes beyond entity page creation to extract cited ideological positions, track thought evolution, and enable ongoing RSS monitoring for thought updates.
Query the blogwatcher-cli SQLite database for RSS scan results. Use pre-verified column names and query templates to avoid errors.
| name | x-account-enrichment |
| description | Enrich skeleton X/Twitter account entity pages to full quality (8-15KB), matching antirez-com.md / simon-willison.md depth. |
| category | wiki |
Enrich skeleton entity pages for X/Twitter accounts tracked in ~/x-accounts.yaml.
⚠️ CRITICAL: Git History Check First Before enriching ANY page, check if a richer version exists in git history. Use
bash config/hermes/skills/wiki/wiki-entity-enrichment-from-article/references/find-richest-version.sh wiki/entities/<handle>.md 3. If the richest version has >50 more lines than current, restore it first, then enrich on top. Seewiki-entity-enrichment-from-article→references/pre-write-verification.md→ "Git History Enrichment" for the full pattern.
Audit current state:
python3 -c "
import os, yaml
with open(os.path.expanduser('~/x-accounts.yaml')) as f:
accounts = [a['handle'].lstrip('@') for a in yaml.safe_load(f)['accounts']]
entity_dir = os.path.expanduser('~/wiki/entities')
for handle in accounts:
path = os.path.join(entity_dir, f'{handle}.md')
if os.path.exists(path):
with open(path) as f: content = f.read()
skeleton = 'status: skeleton' in content
enriched = 'Core Ideas' in content
print(f' {handle}: skeleton={skeleton}, enriched={enriched}')
else:
print(f' {handle}: MISSING')
"
Prioritize by tiers:
/home/exedev/wiki/entities/{name}.md)Post-batch verification:
# Check file sizes
ls -la ~/wiki/entities/*.md | sort -k5 -n -r | head -30
# Find remaining skeletons
grep -l 'status: skeleton' ~/wiki/entities/*.md
# Find duplicates (skeleton + enriched for same person)
# Common pattern: full-name-slug.md vs handle.md
Cleanup duplicates:
# Delete skeleton duplicates after confirming enriched version exists
rm ~/wiki/entities/ethan-mollick.md # → emollick.md
rm ~/wiki/entities/chip-huyen.md # → chipro.md
rm ~/wiki/entities/lilian-weng.md # → lilianweng.md
rm ~/wiki/entities/eugene-yan.md # → eugeneyan.md
rm ~/wiki/entities/samuel-colvin.md # → samuelcolvin.md (also empty)
rm ~/wiki/entities/benjamin-clavi.md # → bclavie.md
rm ~/wiki/entities/cl-mentine-fourrier.md # → clefourrier.md
rm ~/wiki/entities/late-interaction.md # concept, not person
Commit and push:
cd ~/ai-topics && git add wiki/ && git commit -m "wiki: enrich X accounts (batch N)" && git push
---
title: "Full Name"
handle: "@twitter_handle"
created: 2026-04-10
updated: 2026-04-10
tags: [person, topic1, topic2]
aliases: ["handle", "alt-name"]
---
# Full Name (@handle)
| | |
|---|---|
| **X** | [@handle](https://x.com/handle) |
| **Blog** | [URL](URL) |
| **GitHub** | [username](https://github.com/username) |
| **Role** | Job title |
| **Known for** | Key contributions |
| **Bio** | 2-3 sentence background |
## Overview
2-3 paragraph introduction of who they are, their background, and why they matter in AI.
## Core Ideas
Their key viewpoints, theories, and opinions on LLM/AI Agent technologies. Use subsections for each major theme. Quote their actual posts/articles where possible.
## Key Work
- Project/tool/library they created
- Papers published
- Notable blog posts
- Talks and presentations
## Blog / Recent Posts
Key articles they've written with dates and summaries.
## Related People
Connections to other wiki entities.
## X Activity Themes
What they tweet about most frequently.
status: skeleton tag[[entity-name]] formatFilename aliasing: Subagents create files with different names than specified (e.g., hynek-schlawack.md instead of hynek.md). Always audit post-batch for duplicates.
Budget exhaustion: 50-iteration budget per subagent. When processing 5 entities, subagent may hit limit and skip writing some files. Check exit_reason: max_iterations in results.
Path discipline: delegate_task subagents must always target ~/wiki/entities/. If a delegated context shows ~/.hermes/home/..., treat it as a runtime artifact and keep writing to the canonical wiki path only.
Status cleanup needed: Even when subagents write content successfully, status: skeleton in frontmatter is often NOT removed. Always verify and manually replace with status: complete if needed.
Successful pattern confirmed (2026-04-10): 8 entities enriched in 4 parallel batches of 2 each, completed in ~6 minutes with file sizes 12.5-18.7KB (exceeding 8-15KB target). This confirms the 2-per-subagent batching strategy works well.
For each person: