Loading…
Read a web source — an article OR a non-article (GitHub repo, project homepage, service site) — and write a TIL document (in Korean). The H1 title is written in Korean. Published pieces (articles, posts, papers, tweets, videos) get a `원문: [원문 제목](URL)` titled-link source line and a `## 요약` section; non-articles get bare `<URL>` line(s) with NO `원문:` label, no titled link, and a fitting first heading like `## 소개`. Body structure follows the source's own job — analytical for a piece that argues, practical for one that teaches. The document shape is a closed spec enforced by scripts/check_format.py, which must print OK before the file is reported as written. Takes a URL as an argument. Use when the user asks to analyze an article/repo/site, document it, or organize a technical post.
analyze-article is an agent skill entry in ChatHome Skills, sourced from GitHub Skill Search and scored 58/100. Read a web source and write a TIL document whose structure follows what the source is for: analytical when it argues, practical when it teaches. **The output do. As an agent skill, it packages a reusable instruction set that AI coding agents such as Codex and Claude Code can load to perform this task without hand-written glue code. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding analyze-article to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
codex skill install ahastudio/tilReview the upstream source before running this command.
Scan coverage: Install metadata and the indexed document body.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
Read a web source and write a TIL document whose structure follows what the source is for: analytical when it argues, practical when it teaches. **The output document MUST be writt