Query crypto project details, Web3 investor info, funding rounds, trending projects, and personnel job changes from RootData. Use this skill when the user asks about blockchain projects, crypto investors, Web3 funding history, investment rounds, trending crypto projects, or personnel movements in th
Documents
投融资日报
Fetch financing event lists from the iYiou skill API and generate daily or recent-N-days financing reports in Markdown to stdout. Use when the task asks to p...
What it does
Fetch financing event lists from the iYiou skill API and generate daily or recent-N-days financing reports in Markdown to stdout. Use when the task asks to p...
The skill document
Daily Investment Digest
Overview
- Pull investment/financing events from
https://api.iyiou.com/skill/info. - Normalize fields, deduplicate rows, and generate a structured Chinese investment report.
Workflow
- One-command full report (recommended, default uses yesterday).
node "{baseDir}/scripts/run_full_report.mjs" \
--max-page 5
- If user explicitly asks for today's report, pass today's date.
node "{baseDir}/scripts/run_full_report.mjs" \
--report-date 2026-03-11 \
--max-page 5
- If user asks for recent 2-7 days, use
--recent-days.
node "{baseDir}/scripts/run_full_report.mjs" \
--recent-days 7
- Direct output mode (stdout only, no file).
node "{baseDir}/scripts/fetch_events.mjs" \
--recent-days 3 \
--stdout-json | \
node "{baseDir}/scripts/generate_report.mjs" \
--input-json - \
--top-n 0 \
--stdout
Path Safety
- Always call scripts with quoted
{baseDir}paths to avoid whitespace-path issues. - Scripts resolve relative input paths against the skill root directory.
Required API Rules
- Use
pageSize=10. - Start at
page=1. - Increment
pageby 1 each request. - Single-day mode: stop when
page>5or API event list is empty. - Recent-N-days mode (
N=2..7): fetch up to the hard limit of 250 records, i.e.pageSize=10andpage<=25, then filter bycreatedAt. - Parse response strictly by schema:
response.code->response.data.posts. - Treat non-zero
codeas API failure. - Retry failed requests up to 3 times before skipping a page.
Script Interfaces
scripts/run_full_report.mjs
- One-command pipeline: fetch + generate
- Defaults to full output (
top-n=0) - Supports
--report-date,--recent-days,--max-page,--page-size,--timeout-seconds,--retry,--delay-seconds - Supports
--top-n(0means all events)
scripts/fetch_events.mjs
--page-sizedefault10--max-pagedefault5for single-day mode, forced to25for recent-N-days mode--report-datedefault yesterday (YYYY-MM-DD) and acts as range end date--recent-dayssupports1..7;1means a single-day report,2..7means recent-N-days report--timeout-secondsdefault15--retrydefault3--delay-secondsdefault0- Always prints JSON to stdout (
--stdout-jsonkept only for compatibility) - Numeric args are bounded for safety:
recent-days[1,7],page-size[1,100],max-page[1,25],retry[1,10]
scripts/generate_report.mjs
--input-jsonrequired--top-ndefault0(0means all events)- Always prints report text to stdout (
--stdoutkept only for compatibility) - Numeric args are bounded for safety:
top-n[0,500]
Output Files
- Disabled by design. This skill is stdout-only and does not write report artifacts to disk.
Data Mapping
- Follow field_mapping.md for source-to-target mapping and fallback rules.
- To reduce context size, the fetch output keeps only:
brief,createdAt,originalLink,postTitle,tags.
Failure Handling
- Continue on single-page failure after retries.
- Use progressive retry backoff (
0.5s,1.0s,1.5s, ...). - Record page-level errors in output JSON
meta.errors. - Generate a report even when no events are found, and clearly mark it as an empty-day report.
Output Policy
- Date policy: default to yesterday for single-day reports; only use today when the user explicitly asks for today.
- Window policy: support
最近两天、最近三天...最近一周by mapping to--recent-days 2..7. - If user asks full detail, run with
--top-n 0. - Use script stdout as the main body and keep event entries unchanged.
- The scripts are responsible only for fetching, filtering, deduplicating, and rendering the event list plus basic statistics.
- The ending section
投资事件总结must be added by the AI in the final response, not by the scripts. - Output order is mandatory:
- First output the full event list.
- Each event must include:
公司简称、轮次、投资方、事件摘要、来源链接. - After the full event list, the final AI response must append one ending section titled
投资事件总结.
- Do not place
投资事件总结before event entries.
Quick Checks
- Run fetch step and confirm
meta.total_unique_events > 0on active days. - In recent-N-days mode, confirm
meta.recent_daysandmeta.range_start_dateare present andmax_page=25. - Run report step and confirm stdout contains:
核心数据概览融资事件按行业分类
- In final AI response, confirm order:
- Event list appears first and each item includes
公司简称、轮次、投资方、事件摘要、来源链接. 投资事件总结appears only after the event list.投资事件总结appears exactly once at the end.
- In final AI response, confirm the AI appends:
投资事件总结
Example End-to-End Command
node "{baseDir}/scripts/run_full_report.mjs" \
--recent-days 7
Related skills
AI news intelligence and daily briefing powered by CellCog. News digests, competitive intelligence, market updates, trend monitoring, industry reports, current events research. Multi-source synthesis for accurate, comprehensive briefs.
Turn any industry into a daily intelligence briefing. An AI agent searches, filters, writes, and delivers structured daily briefs to 9 channels — with machine-checked formatting and a business review gate. Ships with a Data+AI profile out of the box; switch to any domain via config.
Financial analysis from single-stock metrics to DCF models and portfolio optimization, delivered as dashboards, PDFs, or Excel.
Citation-backed research reports across markets, competitors, investments, and academic topics via the CellCog agent.
Use when the user needs Tonghuashun iFinD market, report, factor, screening, calendar, or other financial data, and all data must come from iFinD after succe...