kr-daily-market-news
Skill2 starsChanged 12 days agoMITView on GitHub
Build a dated Korean daily market-news report for the whole market and sectors, using domestic RSS articles plus Google News RSS discovery signals, then write Markdown/JSON artifacts and a Naver Blog publish manifest.
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- kr-analyst-report-discoverSkill
- kr-analyst-report-fetchSkill
- kr-analyst-report-insightSkill
- kr-analyst-report-watchSkill
- kr-article-readabilitySkill
- kr-chatgpt-reviewSkill
- kr-earnings-reviewSkill
- kr-finance-slide-claritySkill
- kr-foreign-analystSkill
- kr-market-leadersSkill
- kr-market-sentimentSkill
- kr-naver-bloggerSkill
- kr-naver-blog-publishSkill
- kr-naver-browseSkill
- kr-naver-insightSkill
- kr-order-backlog-analysisSkill
- kr-portfolio-guardSkill
- kr-portfolio-monitorSkill
- kr-research-siteSkill
- kr-sector-analysisSkill
- kr-sector-auditSkill
- kr-sector-compareSkill
- kr-sector-data-packSkill
- kr-sector-planSkill
- kr-sector-updateSkill
- kr-stock-analysisSkill
- kr-stock-chartSkill
- kr-stock-dart-analysisSkill
- kr-stock-data-packSkill
- kr-stock-planSkill
- kr-stock-updateSkill
- kr-strategy-backtestSkill
- kr-trade-flow-analysisSkill
- kr-web-browseSkill
- telegram-report-senderSkill
- us-daily-market-newsSkill
- us-earnings-reviewSkill
- us-sec-analysisSkill
- us-stock-analysisSkill
- us-strategy-backtestSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create a daily Korean market-news report for Codex Desktop Automation.
- Very specific: line 31
If the user asked for blog publication, hand the generated manifest to kr-naver-blog-publish.
- Very specific: line 53
no top metadata bullets (기준일, 생성시각, 수집모드).
- Distinctive: line 56
no Markdown bullet lines anywhere in the Naver post
- Very specific: line 57
no Markdown links or — source suffixes inside the Naver 시장 주요 뉴스 section
- Very specific: line 63
Default live collection uses domestic media RSS article URLs for body sections.
- Distinctive: line 70
Run before considering changes complete:
- Very specific: line 78
Use --fixture <fixture.json> only for deterministic tests or dry runs.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Korean Daily Market News
Create a daily Korean market-news report for Codex Desktop Automation. This skill is intended for scheduled local-project runs, not launchd, cron, or GitHub Actions.
Workflow
- Read references/workflow.md.
- Optionally accept the watchlist JSON for compatibility, but do not collect watchlist stock news or watchlist DART/KRX links in this daily market-news report.
Collect market and sector RSS news flow:
node skills/kr-daily-market-news/scripts/fetch-daily-market-news.js \ --json-out analysis-example/kr-market/daily-news-YYYY-MM-DD.jsonRender the report and blog publish manifest:
node skills/kr-daily-market-news/scripts/render-daily-report.js \ --json analysis-example/kr-market/daily-news-YYYY-MM-DD.json \ --md-out analysis-example/kr-market/daily-news-YYYY-MM-DD.md \ --post-out analysis-example/kr-market/naver-post-YYYY-MM-DD.md \ --manifest-out analysis-example/kr-market/naver-publish-YYYY-MM-DD.json- If the user asked for blog publication, hand the generated manifest to
kr-naver-blog-publish. Scheduled public publishing is allowed only through that skill's explicit scheduled mode and only if validation passes.
Output Contract
- Main artifacts:
analysis-example/kr-market/daily-news-YYYY-MM-DD.jsonanalysis-example/kr-market/daily-news-YYYY-MM-DD.md
- Blog artifacts:
analysis-example/kr-market/naver-post-YYYY-MM-DD.mdanalysis-example/kr-market/naver-publish-YYYY-MM-DD.json
- The research Markdown (
daily-news-YYYY-MM-DD.md) must include:기준일 / 생성시각오늘 시장 한 줄시장 주요 뉴스업종/테마별 흐름공식 공시/자료리더십 스크린 요약when a same-date leaders artifact exists블로그 제목 후보출처- investment disclaimer
- The Naver Blog Markdown (
naver-post-YYYY-MM-DD.md) must use the SmartEditor-ready format:- no
오늘 시장 한 줄 - no top metadata bullets (
기준일,생성시각,수집모드); the title is followed directly by시장 주요 요약 시장 주요 요약as a 1-5 numbered summary list시장 주요 뉴스as raw link-card input lines only:1. 기사 제목, next linehttps://..., then a blank line before the next item- no Markdown bullet lines anywhere in the Naver post
- no Markdown links or
— sourcesuffixes inside the Naver시장 주요 뉴스section - no
블로그 제목 후보 - no
관심종목 뉴스 업종/테마별 흐름as the fixed 10-sector table출처as a two-column내용 | 링크table
- no
- Live news collection must include only articles whose normalized publication date matches
asOfDate; RSSpubDatevalues are normalized to KSTYYYY-MM-DD. - Default live collection uses domestic media RSS article URLs for body sections. Google News RSS is discovery-only and must not populate
marketNews,sectorNews, Naver postlinkCards, or the rendered출처table. - Articles with unknown dates or non-matching dates stay out of the JSON body sections and post body; record the exclusion in JSON
warnings. - The Naver post must not show
## 수집 경고near the top. Summarize collection gaps at the end near the disclaimer under### 수집 참고, without exposing long URLs. - The Naver publish manifest must set
post.titleto the first title candidate and, for daily market-news only, must setpost.linkCardsto the raw URLs shown in the Naver시장 주요 뉴스section, in the same order.
Validation
Run before considering changes complete:
node skills/kr-daily-market-news/scripts/test-daily-market-news.js
node --check skills/kr-daily-market-news/scripts/fetch-daily-market-news.js
node --check skills/kr-daily-market-news/scripts/render-daily-report.jsUse --fixture <fixture.json> only for deterministic tests or dry runs. Do not treat fixture output as a real same-day market report.
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.

