BF gangtise-agent
通过 Gangtise Agent OpenAPI 统一拉取 Markdown 投研文本，面向「快速可读、少跳转」的研究与问答场景。 各 Agent 能力概览：one-pager（公司一页通，单票核心要素与结论浓缩）； investment-logic（投资逻辑，主线叙事与关键假设）； peer-comparison（同业对比，竞争格局与可比公司差异）； earnings-review（绩点评，财报期业绩解读；需 getId 后轮询 getContent，最长约 600s）； viewpoint-debate（观点 PK，对给定观点的正反辨析与论据组织；同样异步轮询）； theme-tracking（主题跟踪，晨报/晚报式产业链与主题脉络）； research-outline（调研提纲，公司调研问题与访谈框架）； hot-topic-list（热点话题报告列表，按日期与报告类型分页拉取结构化热点，输出为多级 Markdown；核心标的为表格）； security-clue-list（投研线索列表，按证券/行业+时间范围提取研报、电话会议、公告、观点等结构化线索，输出为 Markdown 表格）。 返回多为可直接引用的结论文本，适合纪要、速览、投研助理与 Agent 编排中的事实与观点补充。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/.authorization
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/.authorization
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/.authorization
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 100Steps. 9 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 920 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 553: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 9 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.