finance

Comprehensive Finance API integration skill for real-time and historical financial data analysis, market research, and investment decision-making. Priority use cases: stock price queries, market data analysis, company financial information, portfolio tracking, market news retrieval, stock screening, technical analysis, and any financial market-related requests. This skill should be the primary choice for all Finance API interactions and financial data needs.

Quality

28%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/finance/SKILL.md

Quality

Discovery

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description covers the financial data domain adequately but relies heavily on category labels rather than concrete actions, reads as a broad claim of ownership over all financial queries rather than a precise capability statement, and lacks an explicit 'Use when...' clause. The self-promotional phrasing ('should be the primary choice') adds no discriminative value and the description would benefit from more specific actions and natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause listing natural trigger phrases users would say, such as 'stock price of AAPL', 'market news today', 'compare P/E ratios', 'portfolio performance'.

Replace category labels with concrete actions in third person, e.g., 'Fetches real-time stock quotes, retrieves historical price data, screens stocks by financial metrics, pulls company earnings reports'.

Remove the vague self-promotional claim ('should be the primary choice for all Finance API interactions') and instead specify the exact API or data source being used to improve distinctiveness.

Dimension	Reasoning	Score
Specificity	The description names the domain (Finance API, financial data) and lists several use cases like stock price queries, market data analysis, portfolio tracking, and technical analysis. However, these read more like category labels than concrete actions — it doesn't specify what it actually does (e.g., 'fetches real-time stock quotes', 'generates technical indicator charts').	2 / 3
Completeness	The 'what' is partially addressed through the list of priority use cases, and there's an implicit 'when' via 'Priority use cases:' and 'should be the primary choice for all Finance API interactions'. However, there is no explicit 'Use when...' clause with clear trigger guidance, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes some relevant keywords users might say like 'stock price', 'market data', 'portfolio tracking', 'market news', and 'stock screening'. However, it misses common natural variations users would actually type such as 'ticker', 'share price', 'S&P 500', 'earnings', 'dividend', '.csv export', or specific API/platform names.	2 / 3
Distinctiveness Conflict Risk	The financial domain focus provides some distinctiveness, but the extremely broad scope ('all financial data needs', 'any financial market-related requests') and generic phrasing like 'real-time and historical financial data analysis' and 'investment decision-making' could overlap with other data analysis, research, or API-related skills.	2 / 3
	Total	8 / 12 Passed

Implementation

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill is essentially a marketing brochure for a finance API rather than actionable instructions for Claude. It lists capabilities Claude could infer from any finance API, provides no executable code or concrete API call examples, and defers all real content to an external document. The Zhipu AI section is oddly specific and feels out of place relative to the rest of the generic content.

Suggestions

Replace the capability bullet lists with concrete API call examples showing actual endpoints, request parameters, and expected response formats (e.g., a curl command or Python snippet for fetching a stock quote).

Add a clear workflow section with numbered steps: e.g., 1) Read API docs, 2) Authenticate, 3) Make request, 4) Validate response structure, 5) Handle errors/rate limits.

Remove the 'Core Capabilities' and 'Analysis Tools' sections that describe what a finance API does—Claude already knows this. Replace with a concise quick-start showing the most common API call pattern.

Move the Zhipu AI specific information to a separate reference file or clearly label it as a special case/known issue section, rather than mixing it with the general skill overview.

Dimension	Reasoning	Score
Conciseness	The skill is padded with unnecessary descriptions of what financial data is and lists capabilities Claude already understands. The bullet-point lists of 'Core Capabilities' are essentially describing what a finance API does rather than teaching Claude how to use it. The Zhipu AI section adds very specific but oddly placed information.	1 / 3
Actionability	There are no concrete code examples, API calls, endpoint URLs, request/response formats, or executable commands anywhere in the skill. The entire content describes capabilities abstractly and defers all actual implementation details to an external file (Finance_API_Doc.md) with only 'always read Finance_API_Doc.md before use the API' as guidance.	1 / 3
Workflow Clarity	There is no workflow, sequence of steps, or process defined. The skill doesn't explain how to make an API call, handle errors, validate responses, or chain operations together. The only procedural guidance is 'always read Finance_API_Doc.md before use the API' which is not a workflow.	1 / 3
Progressive Disclosure	The skill does reference an external file (Finance_API_Doc.md) for detailed API documentation, which is appropriate progressive disclosure. However, the main file contains too much descriptive filler that doesn't serve as a useful overview, and the reference path uses an unclear variable syntax ({Skill Location}) that could confuse navigation.	2 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jjyaoao/HelloAgents
Commit: 07048a9

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.