agentleFS
kidowkidow/skills/stock-analysis/SKILL.md

stock-analysis

Skill2 starsChanged 6 months agoMITView on GitHub

Analyzes a Korean stock by name using the pykrx MCP server and DART, calling tools in order to assemble valuation, financial statements, investor flow, and short-selling data into a single investment-value report. Use when the user asks whether to buy a Korean stock, asks for its investment value, or requests a financial analysis of a listed Korean company (e.g. 삼성전자, 카카오, NAVER).

  • Reads credentials

27 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use pet-commerce-creator, product-marketing-copywriter and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • dycnnnbSkill

    pet-commerce-creator

    萌宠带货短视频全流程创作技能,基于COZE视频大模型API,支持萌宠剧情/好物测评/品种科普/宠品带货等全类型创作,覆盖爆款解析反推、知识库联动、互动优化、素材批量下载、全素材整合,实现从创意到带货引流型成品视频的自动化生成,适配15-30秒竖屏9:16主流平台规格。

    Also in 3 projects that use this

  • dycnnnbSkill

    product-marketing-copywriter

    产品营销文案创作技能,支持多品类产品的吸引性营销文案生成,适用于产品推广、品牌营销、销售转化

    Also in 3 projects that use this

  • buildoakSkill

    moltbook

    Also in 4 projects that use this

  • ArogyaReddySkill

    tailored-resume-generator

    Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

    Also in 4 projects that use this

  • AnthropicSkill

    contract-review

    Lightweight NDA, MSA, and vendor contract review for SMBs without legal on staff. Reads contracts from local files, mail attachments (Gmail or M365), a connected file store (Google Drive or M365), or DocuSign envelopes; flags non-standard terms; explains risks in plain English; and outputs a marked-up redline as a separate DOCX. Use when the user says "review this contract," "what am I signing," "red flags," "flag any concerns," "check the payment terms," or uploads/forwards a contract or legal agreement.

    Also in 4 projects that use this

  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 3 projects that use this

  • +3 more from dycnnnb

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 3

    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
  1. Very specific:

    Dates: every date argument is YYYYMMDD with no dashes.

    line 14
  2. Very specific:

    Call it with the stock name.

    line 32
  3. Very specific:

    If multiple candidates are returned, pick the one whose corp_name exactly matches the input (prefer the listed company).

    line 33
  4. Very specific:

    If no ticker can be resolved at all → output 종목을 찾을 수 없습니다 and stop.

    line 37
  5. Distinctive:

    Read the recent 공매도 거래량/비중 trend.

    line 83
  6. Distinctive:

    After all steps, output this report in Korean.

    line 106
  7. Distinctive:

    Always state this is a data-based judgment, not an investment recommendation.

    line 156

“Common” is measured: kept by at least 6 in 10 of the 13 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Korean Stock Analysis

You are a Korean equity analyst. Given a stock name, call the pykrx MCP tools (and DART tools served by the same server) in order, collect the data, compute derived metrics, and produce one investment-value report. This is a data-driven reference, not investment advice.

Requirements

  • MCP server: pykrx must be connected (tools named mcp__pykrx__*). If it is not available, tell the user to connect it and stop.
  • DART_API_KEY: the financial-statement and corp-code tools require the DART_API_KEY environment variable on the MCP server. The skill cannot read env vars directly — it detects availability by attempting the first DART call (Step 1) and reading the error. If DART is unavailable, run in pykrx-only mode (see Step 1).
  • Dates: every date argument is YYYYMMDD with no dashes.

Input

A stock name. Examples: 삼성전자, 카카오, NAVER. If the user gives a 6-digit code instead, use it directly as the ticker and still resolve corp_code via Step 1 for the financials.


Task

Step 0. Set the date range

  • end_date = today (YYYYMMDD). start_date = 3 months before today.
  • Markets close on weekends/holidays, so the latest calendar day may have no data. Always read the most recent populated row within the range, never assume end_date itself has data.
  • Reuse this range for every ranged tool call below.

Step 1. Resolve the company (ticker + corp_code)

Tool: get_dart_corp_code(name) → returns corp_code (8-digit), corp_name, stock_code (= 6-digit ticker), ceo_name.

  • Call it with the stock name. Use the returned stock_code as the ticker and corp_code for all DART steps.
  • If multiple candidates are returned, pick the one whose corp_name exactly matches the input (prefer the listed company).
  • If the call fails with a missing-key / auth error → DART is unavailable. Tell the user: DART_API_KEY가 설정되지 않아 재무제표·파생지표 분석은 제외하고 진행합니다. Then enter pykrx-only mode:
    • Resolve the ticker via get_market_ticker_list(today, "KOSPI") then "KOSDAQ", matching the name with get_market_ticker_name(ticker). This is expensive — only fall back here when DART is down.
    • Skip Steps 4–5; mark all financial/derived metrics as 조회 불가.
  • If no ticker can be resolved at all → output 종목을 찾을 수 없습니다 and stop.
  • Print the resolved ticker, corp_code, and name before continuing.

Step 2. Price & market-cap context

Tool: get_market_cap_by_date(ticker, start_date, end_date)

  • From the most recent populated row, record 시가총액, 상장주식수, and 종가 (current price). These head the report for context.

Step 3. Valuation

Tool: get_market_fundamental_by_date(ticker, start_date, end_date)

  • From the most recent populated row, record: PER, PBR, EPS, BPS, DIV (배당수익률), DPS.
  • Judge on absolute thresholds (no industry comparison):
    • PER <10 저평가 가능성 · 10–20 적정 · >20 고평가 가능성
    • PBR <1 장부가 이하 · 1–2 적정 · >3 고평가 주의

Step 4. Financial statements (DART) — skip in pykrx-only mode

Tools (in order): get_dart_income_statement → get_dart_balance_sheet → get_dart_cash_flow, all called as (corp_code, year, "11011").

  • year = last completed fiscal year. Try the prior calendar year first (e.g. "2025"); if the result is empty (report not yet filed), retry with the year before ("2024"). Record which year was used.
  • DART returns both 연결(CFS) and 별도(OFS) line items — prefer 연결(CFS). Account names vary across filers; match flexibly:
    • 매출액 ≈ 매출액 / 수익(매출액) / 영업수익
    • 영업이익, 당기순이익, 자산총계, 부채총계, 자본총계 — match by closest standard label.
    • 영업활동 현금흐름 ≈ 영업활동으로인한현금흐름 / 영업활동현금흐름.
  • Extract — IS: 매출액, 영업이익, 당기순이익. BS: 자산총계, 부채총계, 자본총계. CF: 영업활동 현금흐름.

Step 5. Derived metrics — skip in pykrx-only mode

Compute from Step 4. If an input is missing, output -.

지표계산식판단 기준
ROE당기순이익 ÷ 자본총계 × 10015% 이상 우량
부채비율부채총계 ÷ 자본총계 × 100200% 초과 주의
영업이익률영업이익 ÷ 매출액 × 10010% 이상 양호
순이익률당기순이익 ÷ 매출액 × 100-
영업 현금흐름현금흐름표 값 직접 확인음수면 주의

Step 6. Investor flow

Tool: get_market_trading_volume_by_investor(start_date, end_date, ticker)

  • Over the range, determine net direction (순매수 + / 순매도 −) for 기관 / 외국인 / 개인.
  • 외국인 + 기관 동시 순매수 → 강한 매수 신호 · 동시 순매도 → 주의 · 개인만 순매수 → 중립.

Step 7. Short selling

Tool: get_shorting_status_by_date(ticker, start_date, end_date)

  • Read the recent 공매도 거래량/비중 trend. Increasing trend → 단기 하락 압력 신호.

Scoring rubric

Score five axes, then sum (0–10). An axis whose data is 조회 불가 scores 1 (중립) and is flagged in the report.

축2점1점0점
밸류에이션 (PER·PBR)저평가적정고평가
수익성 (ROE·영업이익률)둘 다 기준 충족하나 충족둘 다 미달
재무안정성 (부채비율·영업CF)부채비율<200% & 영업CF>0하나만 충족둘 다 위험
수급 (외국인·기관)동반 순매수혼조동반 순매도
공매도비중 감소/낮음보합증가

Stars from total: 9–10→⭐⭐⭐⭐⭐ · 7–8→⭐⭐⭐⭐ · 5–6→⭐⭐⭐ · 3–4→⭐⭐ · 0–2→⭐ Conclusion from stars: ⭐⭐⭐⭐ 이상 → ✅ · ⭐⭐⭐ → ⚠️ · ⭐⭐ 이하 → ❌


Output

After all steps, output this report in Korean.

### 📊 [종목명] 투자 가치 분석 리포트

**기준일**: {오늘 날짜}  ·  **현재가**: {종가}  ·  **시가총액**: {시가총액}

#### 1. 밸류에이션
| 지표 | 값 | 판단 |
|------|----|------|
| PER  | -  | -    |
| PBR  | -  | -    |
| EPS  | -  | -    |
| BPS  | -  | -    |
| 배당수익률 | - | - |

#### 2. 수익성 (재무제표 기반 · {사용 사업연도})
| 지표 | 값 | 판단 |
|------|----|------|
| ROE  | -% | -    |
| 영업이익률 | -% | - |
| 순이익률 | -% | - |
| 부채비율 | -% | - |
| 영업 현금흐름 | - | - |

#### 3. 수급 (최근 3개월)
- 외국인: 순매수 / 순매도
- 기관: 순매수 / 순매도
- 개인: 순매수 / 순매도

#### 4. 공매도
- 최근 추이: 증가 / 감소 / 보합

#### 5. 종합 의견

**투자 매력도**: ⭐ (총 {0~10}점 / 5축 가중치 기준)

긍정 요인과 부정 요인을 각각 bullet로 정리한 뒤, 아래 중 하나로 결론:

- ✅ **매수 고려 가능**: 저평가 + 양호한 재무 + 수급 우호
- ⚠️ **추가 관찰 필요**: 일부 지표 혼재, 단기 관망 권고
- ❌ **현시점 매수 비추천**: 고평가 또는 재무 리스크 존재

> ⚠️ 본 분석은 공개 데이터 기반의 참고 자료이며, 투자 결정의 책임은 본인에게 있습니다.

Constraints

  • On any single tool failure, mark that item 조회 불가 and continue the rest of the analysis.
  • Uncomputable derived metrics are -.
  • Always state this is a data-based judgment, not an investment recommendation.
  • Respond entirely in Korean.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.