asgard-ai-platform/grad-pecking-order
Apply pecking order theory (Myers and Majluf, 1984) to analyze how information asymmetry drives financing hierarchy decisions. Use this skill when the user needs to explain why firms prefer internal over external financing, interpret equity issuance as a negative signal, evaluate capital raising decisions, or when they ask 'why did the stock drop on the equity offering', 'should we use debt or equity', or 'why do firms hoard cash'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-pecking-order
Pecking order theory (Myers & Majluf, 1984) argues that firms follow a strict financing hierarchy — internal funds first, then debt, then equity — driven by information asymmetry between managers and outside investors. Unlike tradeoff theory, there is no target leverage ratio.
IRON LAW: Firms prefer internal financing first because external
financing signals negative private information. Equity issuance is
the most informationally sensitive — and therefore most costly — source.
Key assumptions:
| Source | Adverse Selection Cost | Pecking Order Rank |
|--------|----------------------|-------------------|
| Retained earnings | None | 1st (preferred) |
| Bank debt (secured) | Low | 2nd |
| Public debt (bonds) | Medium | 3rd |
| Convertible debt | Medium-High | 4th |
| Equity issuance | Highest | Last resort |
## Pecking Order Analysis: [Firm / Decision]
### Information Environment
- Asymmetry level: [High / Medium / Low]
- Key drivers: [R&D intensity, asset complexity, etc.]
### Financing Decision
| Option | Available | Adverse Selection Cost | Chosen? |
|--------|-----------|----------------------|---------|
| Internal funds | [Y/N] | None | [Y/N] |
| Debt | [Y/N] | [Low/Medium] | [Y/N] |
| Equity | [Y/N] | [High] | [Y/N] |
### Signaling Implications
- [Expected market reaction and rationale]
### Assessment
- [Consistent with pecking order? If not, why?]
Take asgard-ai-platform/grad-pecking-order from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.