liquidity-analysis
Skill0 starsChanged 46 days agoMITView on GitHub
Identify and explain portfolio liquidity risks using approved liquidity metrics and classifications.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilltheir own version, first seen Sep 28, 2026
- Serennity007/claude-trading-skills-67their own version, first seen Aug 25, 2026
- agiprolabs/claude-trading-skillstheir own version, first seen Mar 11, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- agiprolabs/claude-trading-skills★ 366same name
- IngAs8/ClaudeSkill★ 0same name
- Serennity007/claude-trading-skills-67★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- skillevaluator-masterySkill
- skillevaluator-masterySkill
- benchmark-comparisonSkill
- concentration-analysisSkill
- exposure-analysisSkill
- m1-tier3-smokeSkill
- market-move-explanationSkill
- performance-attributionSkill
- pm-commentary-generationSkill
- portfolio-change-analysisSkill
- portfolio-overviewSkill
- position-investigationSkill
- risk-explanationSkill
- scenario-analysisSkill
- skillevaluator-masterySkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill when the user request clearly requires the capability described above.
- Distinctive: line 16
Do not activate this skill for unrelated market lookup, general education, or requests that can be answered without this business …
- Distinctive: line 21
Call approved logical capabilities from the Agentic Data Pipeline.
- Distinctive: line 30
Prefer authoritative internal analytical capabilities over independent LLM calculations.
- Distinctive: line 31
Never fabricate a portfolio value, benchmark, position, return, exposure, or risk statistic.
- Very specific: line 40
Use portfolio.positions for position weight, type, and currency as liquidity risk proxies (e.g.
- Distinctive: line 46
Never infer a missing position's weight, type, or currency.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
Files
Liquidity Analysis
Use when
Use this skill when the user request clearly requires the capability described above.
Do not use when
Do not activate this skill for unrelated market lookup, general education, or requests that can be answered without this business capability.
Procedure
- Resolve portfolio, scope, and relevant as-of date(s).
- Call approved logical capabilities from the Agentic Data Pipeline.
- Validate returned dates, identifiers, and coverage.
- Reconcile quantitative claims whenever authoritative totals exist.
- Identify material results rather than narrating every field.
- Explain uncertainty or missing data explicitly.
- Produce a concise PM-oriented answer grounded in tool results.
Data and tool rules
- Prefer authoritative internal analytical capabilities over independent LLM calculations.
- Never fabricate a portfolio value, benchmark, position, return, exposure, or risk statistic.
- Never bypass authorization.
- Preserve source and as-of metadata for quantitative claims.
- In the sandboxed reference evaluation, invoke the staged deterministic bridge
with
python /workspace/repo/synthetic_data_pipeline/tool_cli.py TOOL_NAMEand the relevant flags. Treat its JSON response as the logical-tool result.
Domain rules
- Use
portfolio.positionsfor position weight, type, and currency as liquidity risk proxies (e.g. concentrated weights, derivative/futures positions carrying rollover or margin exposure). - The reference data has no dedicated liquidity classification field. Explicitly disclose that limitation rather than inventing a liquidity score, tier, or classification that does not exist in the tool output.
- Never infer a missing position's weight, type, or currency; report it as unavailable instead.
Output
Provide:
- key conclusion;
- material drivers;
- supporting quantitative evidence;
- important limitations/data gaps.
For traceability, end the response with Workflow: liquidity-analysis
after completing the workflow. This marker is an execution trace, not a
substitute for the supporting evidence.
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
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.

