ai-analyst-lab/.claude/skills/history
.claude/skills/history/SKILL.md
# Skill: History ## Purpose Browse and search past analyses from the analysis archive. Helps users recall what they've analyzed before, find prior findings, and build on previous work. ## When to Use - User says `/history` or "what have I analyzed before?" - At session start, to provide context on prior work - When framing a new question, to check if similar analysis exists ## Invocation `/history` — list recent analyses (last 10) `/history {id}` — show full details for a specific analysis `/
$ install --global
skillsauthnpx skillsauth add ai-analyst-lab/ai-analyst .claude/skills/historyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 3:47 AM4.5s1 file scanned
SKILL.md
Skill: History
Purpose
Browse and search past analyses from the analysis archive. Helps users recall what they've analyzed before, find prior findings, and build on previous work.
When to Use
- User says
/historyor "what have I analyzed before?" - At session start, to provide context on prior work
- When framing a new question, to check if similar analysis exists
Invocation
/history — list recent analyses (last 10)
/history {id} — show full details for a specific analysis
/history search={term} — search by title, question, or tags
/history --all — list all analyses across all datasets
/history dataset={id} — filter to a specific dataset
Instructions
Step 1: Load Archive
- Read
.knowledge/analyses/index.yaml - If empty: "No analyses archived yet. Complete an analysis and it will appear here."
Step 2: Execute Command
List recent (/history):
- Filter to active dataset (unless
--allflag) - Sort by date descending
- Show last 10 as a table: date, title, level, key finding count, dataset
- Show total count: "Showing 10 of {total} analyses."
Show specific (/history {id}):
- Find entry by ID in index
- Display: title, date, question, level, all key findings, metrics used, agents used, output files, tags, confidence, recommendations
- If output files exist, offer: "Want to review the full analysis?"
Search (/history search={term}):
- Search across: title, question, key_findings, tags (case-insensitive)
- Display matching entries as a table
- If no matches: "No analyses match '{term}'. Try broader terms."
All datasets (/history --all):
- Include dataset_id column in output
- Sort by date descending across all datasets
Step 3: Contextual Suggestions
After displaying history:
- "Want to re-run this analysis with fresh data?"
- "Want to build on finding #{n}?"
- If recent analysis was partial: "This analysis was incomplete. Resume with
/resume-pipeline."
Edge Cases
- No active dataset: Show all analyses or prompt to connect
- Archive file missing: Create empty index
- Analysis output files deleted: Note "output files no longer available"
- Very long history (>100): Paginate, show 20 at a time
Related Skills
ai-analyst-lab/.claude/skills/TEMPLATE
testing
VerifiedTrustedCommunity
# Skill: {{BLANK_1_SKILL_NAME}} ## Purpose {{BLANK_2_WHEN_TO_FIRE}} ## When to Use Fires automatically when the user asks Claude to do something that matches the trigger condition above. ## Instructions 1. Detect the trigger condition 2. Execute your guardrail check 3. If the check matters, print a clear, visible warning with "{{BLANK_3_SIGNATURE_PHRASE}}" as the first line 4. Continue with the analysis, incorporating the warning into the output ## Anti-Patterns - Do not fire when the condit
175SKILL.mdUpdated Apr 17, 2026
ai-analyst-lab/.claude/skills/visualization-patterns
development
VerifiedTrustedCommunity
# Skill: Visualization Patterns ## Purpose Ensure every chart Claude Code produces follows high-quality design standards with named themes, consistent styling, and clear data communication. ## When to Use Apply this skill whenever generating a chart, graph, or data visualization. Always apply the active theme unless the user specifies otherwise. Default theme: `minimal`. ## Instructions ### Pre-flight: Load Learnings Before executing, check `.knowledge/learnings/index.md` for relevant entrie
146SKILL.mdUpdated Apr 4, 2026
ai-analyst-lab/.claude/skills/triangulation
development
VerifiedTrustedCommunity
# Skill: Triangulation / Sanity Check ## Purpose Cross-reference analytical findings against multiple data sources, external benchmarks, and common sense to catch errors before they become bad decisions. ## When to Use Apply this skill after every analysis, before presenting findings to stakeholders, and whenever a result seems surprising. If a finding would change a decision, it MUST be triangulated first. ## Instructions ### Triangulation Framework Every finding gets checked through four
146SKILL.mdUpdated Apr 4, 2026
ai-analyst-lab/.claude/skills/tracking-gaps
data-ai
VerifiedTrustedCommunity
# Skill: Tracking Gap Identification ## Purpose Assess whether the data needed for an analysis actually exists, identify what's missing, and produce prioritized instrumentation requests for engineering when gaps are found. ## When to Use Apply this skill after the Data Explorer agent inventories available data, when an analysis requires data that might not exist, or when initial query results suggest incomplete tracking. Run before committing to an analysis approach. ## Instructions ### Gap
146SKILL.mdUpdated Apr 4, 2026