express-improve
Express-Improve: Make Ideas Heard, Understood, and Remembered
This skill is built on the systematic methodology from Patrick Winston’s MIT talk How to Speak, combined with the practical demands of high-stakes communication scenarios such as startup recruiting, research presentations, job talks, and persuasive conversations.
Core belief: Good ideas do not spread on their own. Communication quality = knowledge × practice × (a small amount of talent). Expression is a skill that can be trained systematically, not an inborn gift.
I. Identify the Scenario First, Then Choose the Strategy
When a user request comes in, first determine the following three things:
1. What kind of communication scenario is this?
| Scenario Type | Core Task | Success Standard |
|---|---|---|
| Startup recruiting / persuading a co-founder | Make the other person believe you are working on the right thing and that it is worth betting on | The other person proactively asks, “What can I do?” |
| Research presentation / group meeting / defense | Help non-experts understand, while convincing experts that you are rigorous | Questions focus on future direction, not “What exactly are you doing?” |
| Job Talk | Establish both vision and substantial completed work within 5 minutes | The committee comes away thinking, “This person has direction and has already done real work” |
More from chasepassion/skills
best-java-structure
Java Layered Architecture Design Pattern — A complete implementation guide for the classic five-layer architecture using Spring Boot + MyBatis-Plus. Suitable for bootstrapping new Java projects, refactoring existing architectures, establishing team development standards,and database migration scenarios.
26fastapi-structure-guide
Trigger when the user wants to create a new FastAPI project, add new features, refactor code, or asks about architectural best practices. This skill enforces 2026 clean architecture with SQLModel, Repository Pattern, full async, and production-ready workflow.
7compact
Create a structured continuation handoff checkpoint for long coding or technical conversations when context is tight, the user asks to compact, another model will continue the task, or a clean resume point is needed. Preserve exact technical state, decisions, file paths, commands, blockers, failed attempts, validation status, and next steps. Do not use for generic summaries, meeting notes, or polished end-user documentation.
4bug-fix
Used for locating, reproducing, validating, and fixing software defects. Applicable when the user asks to "fix a bug," "locate an error," "analyze and fix an error," "reproduce an issue," "find the root cause," and similar scenarios.
4log-build
Add or refine sparse, structured, file-persisted application logs for non-trivial code changes. Use when Agent is proposing an implementation approach, writing a plan, or implementing or modifying complex business logic, critical state transitions, validation or parsing flows, boundary interactions (HTTP, DB, cache, queue, filesystem, subprocess), retries, fallbacks, async jobs, concurrency, or background tasks, because planning is the right time to decide log placement. Reuse the project's existing logging infrastructure whenever possible. Do not use for trivial edits, simple obvious CRUD, blanket "log everything" requests, or low-value noise.
4fix-bug
Used for locating, reproducing, validating, and fixing software defects. Applicable when the user asks to “fix a bug,” “locate an error,” “analyze and fix an error” “reproduce an issue,” “find the root cause,” and similar scenarios.
2