exposure-analysis
Skill0 starsChanged 45 days agoMITView on GitHub
Analyze sector, factor, country, currency, and security exposures and identify material concentrations.
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
- liquidity-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. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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 sector/currency/security-level exposure and risk.factor_exposure for factor-level exposure.
- Distinctive: line 44
Never infer a missing exposure or factor value.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Exposure 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 sector/currency/security-level exposure andrisk.factor_exposurefor factor-level exposure. - Include derivative and hedge positions in exposure totals; do not omit a position because it carries a negative or unusual weight.
- Never infer a missing exposure or factor value; 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: exposure-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.

