catalyst-identification
Identify upcoming and recent catalysts that could move the stock
Best use case
catalyst-identification is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Identify upcoming and recent catalysts that could move the stock
Teams using catalyst-identification should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/catalyst-identification/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How catalyst-identification Compares
| Feature / Agent | catalyst-identification | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Identify upcoming and recent catalysts that could move the stock
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
## Catalyst Identification Workflow OBJECTIVE: Find events that could significantly move the stock price. ### Step 1: Search for Upcoming Events - Use `get_news_sentiment` with keywords like "earnings", "conference", "announcement" - Check for scheduled events in the news ### Step 2: Identify Recent Catalysts - Look at news that coincided with significant price moves - What drove the most recent rally or selloff? ### Step 3: Categorize Catalysts - EARNINGS: Quarterly reports (high impact) - PRODUCT: Launches, updates, delays - MANAGEMENT: CEO changes, departures - REGULATORY: FDA approvals, investigations - MACRO: Industry-wide events affecting sector - M&A: Acquisition rumors, deals ### Step 4: Assess Impact Potential For each catalyst, rate: - HIGH IMPACT: Could move stock 5%+ - MEDIUM IMPACT: Could move stock 2-5% - LOW IMPACT: Minor or already priced in ### Output Format UPCOMING CATALYSTS: 1. [Event] - [Date if known] - [Expected Impact] 2. [Event] - [Date if known] - [Expected Impact] RECENT CATALYSTS: 1. [Event] - [What happened] - [Actual Impact] CATALYST WATCH: [Key event to monitor]
Related Skills
bgo
Automated Blender build-go workflow. Automatically builds, removes old version, installs, enables, and launches Blender with your extension/add-on. Use when you want to quickly test changes, execute complete build-to-launch cycle, or run custom packaging scripts with automatic Blender launch.
codereadr-automation
Automate Codereadr tasks via Rube MCP (Composio). Always search tools first for current schemas.
codeinterpreter-automation
Automate Codeinterpreter tasks via Rube MCP (Composio). Always search tools first for current schemas.
code-generation
Use when generating boilerplate code, __init__.py files, or test scaffolds. Provides scripts that generate consistent, convention-following code.
codacy-automation
Automate Codacy tasks via Rube MCP (Composio). Always search tools first for current schemas.
coassemble-automation
Automate Coassemble tasks via Rube MCP (Composio). Always search tools first for current schemas.
clipper
Analyze video transcriptions to identify interesting segments for clipping. Finds highlights, key moments, and reactions with precise timestamps. Use when working with video transcriptions to extract clip-worthy moments. (project)
clink-standalone
Standalone CLI bridge - launch external AI CLIs (gemini, codex, claude) directly without MCP server. Use when you need to delegate tasks to specialized CLI tools with their own context windows. Supports role-based prompts and file references.
client-management
Manage client relationships using the local CRM — add contacts, track deals through the pipeline, schedule follow-ups, log interactions, and generate reports. All data stored locally in SQLite.
clickmeeting-automation
Automate Clickmeeting tasks via Rube MCP (Composio). Always search tools first for current schemas.
cli
Use this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes.
clearout-automation
Automate Clearout tasks via Rube MCP (Composio). Always search tools first for current schemas.