查询基金持有人结构(按报告期)。当用户需要查询基金持有人户数、户均持有份额、机构/个人/前十大持有人份额与比例等,可按 report_type 与 start_date/end_date 过滤时使用。直接返回数组(非分页)。
Scanned 9/2/2026
Install to Claude Code
npx -y skills add FTShare-Lab/FTShare-skill --skill fund-holder-structure-single-fund --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fund Holder Structure Single Fund?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/ftshare-lab-fund-holder-structure-single-fund)More formats (shields.io, HTML) on the badges page.
---
name: fund-holder-structure-single-fund
description: "查询基金持有人结构(按报告期)。当用户需要查询基金持有人户数、户均持有份额、机构/个人/前十大持有人份额与比例等,可按 report_type 与 start_date/end_date 过滤时使用。直接返回数组(非分页)。"
---
# 基金持有人结构
## 接口说明
| 项目 | 说明 |
|----------|-------------------------------------------------------------------|
| 接口名称 | 基金持有人结构 |
| 外部接口 | `/api/v1/market/data/fund/fund-holder-structure` |
| 请求方式 | GET |
## 请求参数
| 参数名 | 类型 | 是否必填 | 描述 |
|--------|------|----------|------|
| `--fund_code` | string | 是 | 基金代码(如 000001 或 000001.OF) |
| `--report_type` | string | 否 | 报告类型:年度报告/中期报告/上市公告书/基金合同生效公告,缺省全部 |
| `--start_date` | int | 否 | 报告期起始日期 YYYYMMDD |
| `--end_date` | int | 否 | 报告期截止日期 YYYYMMDD |
## 执行方式
通过根目录的 `run.py` 调用(推荐):
```bash
python <RUN_PY> fund-holder-structure-single-fund --fund_code 000001 --report_type 年度报告
```
> `<RUN_PY>` 为主 `SKILL.md` 同级的 `run.py` 绝对路径。
## 响应结构
JSON 对象或数组,结构请参考 [ftshare-doc](../..) 接口文档。
## 注意事项
- 必填参数必须提供。
- 响应以 JSON 格式输出至 stdout,诊断信息输出至 stderr。
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.