grad-event-study
Apply event study methodology to measure abnormal returns and cumulative abnormal returns (CAR) around corporate or market events. Use this skill when the user needs to quantify the market impact of announcements, design event and estimation windows, or when they ask 'did this event affect stock price', 'how do I calculate abnormal returns', or 'what is the market reaction to this announcement'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/grad-event-study”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/grad-event-studymetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
62 words · 398 chars — "Apply event study methodology to measure abnormal returns and cumulative abnorma…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 62 words.
Documentation present and substantive
Documentation present (SKILL.md, 706 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Overview
The event study method (Fama et al., 1969; MacKinlay, 1997) isolates the abnormal return attributable to a specific event by comparing actual returns against a model of expected (normal) returns. Cumulative abnormal returns (CAR) over an event window quantify the total market reaction.
When to Use
- Measuring market reaction to earnings announcements, M&A, policy changes, or regulatory events
- Testing semi-strong form market efficiency
- Quantifying the economic significance of corporate disclosures
- Comparing market reactions across different event types or firm characteristics
When NOT to Use
- The event date is ambiguous or the information leaked gradually
- Confounding events overlap with the event window
- The firm's stock is illiquid with many zero-return days
- The event was widely anticipated and fully priced before the event window
Assumptions
IRON LAW: Event study validity requires that the event was UNANTICIPATED —
if the market priced it in before the event window, abnormal returns will
be zero even if the event matters.
Key assumptions:
- Event date is precisely identifiable and the event was unexpected
- No confounding events occur within the event window
- The normal return model is correctly specified during the estimation window
- Market microstructure effects (thin trading, bid-ask bounce) do not distort returns
Methodology
Step 1 — Define Event and Windows
Identify the event date (day 0). Set estimation window (e.g., [-250, -11]) to estimate normal returns. Set event window (e.g., [-1, +1] or [-5, +5]) to capture the reaction.
Step 2 — Estimate Normal Returns
Use the market model: Ri,t = αi + βi × Rm,t + εi,t estimated over the estimation window. Alternatives include constant mean return or Fama-French factors. See references/ for model specifications.
Step 3 — Compute Abnormal and Cumulative Abnormal Returns
AR = Actual return - Expected return for each day in the event window. CAR = sum of ARs over the event window. Compute CAAR (cumulative average abnormal return) across firms.
Step 4 — Statistical Testing
Test H₀: CAR = 0 using parametric tests (cross-sectional t-test, Patell test) and non-parametric tests (sign test, rank test). Report both for robustness.
Output Format
## Event Study: [Event Description]
### Window Design
| Window | Period | Rationale |
|--------|--------|-----------|
| Estimation | [-250, -11] | [rationale] |
| Event | [-1, +1] | [rationale] |
### Abnormal Returns
| Day | AR (%) | t-stat |
|-----|--------|--------|
| -1 | x.xx | x.xx |
| 0 | x.xx | x.xx |
| +1 | x.xx | x.xx |
### Cumulative Abnormal Returns
| Window | CAR (%) | t-stat | p-value | Significant? |
|--------|---------|--------|---------|-------------|
| [-1, +1] | x.xx | x.xx | x.xx | [Yes/No] |
### Cross-Sectional Analysis
- [If applicable: regression of CAR on firm characteristics]
### Limitations
- [Note any confounding events or assumption violations]
Gotchas
- Clustering of event dates (e.g., industry-wide regulation) violates cross-sectional independence
- Short estimation windows produce noisy normal return parameters
- Long event windows increase the probability of confounding events
- Penny stocks and illiquid securities inflate abnormal returns artificially
- The market model assumes constant beta — structural breaks invalidate this
- Publication bias: studies finding zero CAR are rarely published
References
- MacKinlay, A. C. (1997). Event studies in economics and finance. Journal of Economic Literature, 35(1), 13-39.
- Fama, E. F., Fisher, L., Jensen, M. C., & Roll, R. (1969). The adjustment of stock prices to new information. International Economic Review, 10(1), 1-21.
- Kolari, J. W., & Pynnönen, S. (2010). Event study testing with cross-sectional correlation of abnormal returns. Review of Financial Studies, 23(11), 3996-4025.
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/grad-event-study