Apply signaling theory (Spence, 1973) to analyze how agents communicate private information through costly, credible signals under information asymmetry. Use this skill when the user needs to evaluate whether a corporate action serves as a credible signal, analyze dividend or IPO signaling, assess separating vs pooling equilibria, or when they ask 'why do firms pay dividends', 'is this signal credible', or 'how does underpricing signal quality'.
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-signaling
Signaling theory (Spence, 1973) explains how informed parties credibly communicate private information to uninformed parties through costly actions. In finance, firms signal quality through dividends, capital structure, underpricing, and other mechanisms that are too costly for low-quality firms to mimic.
IRON LAW: A signal is credible ONLY if it is costly to fake — cheap
talk is not a signal. For a separating equilibrium, the signal must
be differentially costly: affordable for high-quality types but
prohibitively expensive for low-quality types.
Key assumptions:
| Financial Signal | Sender | Costly Because |
|-----------------|--------|----------------|
| Dividends | Firm managers | Commits cash flow, tax cost |
| IPO underpricing | Issuing firm | Leaves money on the table |
| Debt issuance | Firm managers | Fixed obligations, bankruptcy risk |
| Share buybacks | Firm managers | Depletes cash reserves |
| Education (Spence) | Job applicant | Time, money, effort |
Checklist for credible signal:
## Signaling Analysis: [Corporate Action / Context]
### Information Structure
- Sender: [who] with private info about [what]
- Receiver: [who] making decision about [what]
### Signal Assessment
| Criterion | Assessment |
|-----------|------------|
| Observable? | [Yes/No] |
| Costly? | [Yes/No — how] |
| Differentially costly? | [Yes/No — why] |
| Credible? | [Yes/No] |
### Equilibrium
- Type: [Separating / Pooling / Semi-separating]
- Stability: [Robust / Fragile — why]
### Implications
- [What rational receivers should infer]
- [Strategic recommendation for sender]
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take asgard-ai-platform/grad-signaling 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.