Menu
Rule-based methodology for essay development. Load this index first, then load specific essay type file based on task.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | Developing Essays |
| description | Rule-based methodology for essay development. Load this index first, then load specific essay type file based on task. |
| Essay Type | File to Load |
|---|---|
| College application, PhD statement, "Why X", mentor essay, personal narrative | personal-essays.md |
| Literary analysis, historical analysis, argumentative essay on external topic | analytical-essays.md |
Rule: If essay answers "who am I / what will I do?" → personal. If essay answers "what does this text/event mean?" → analytical.
analytical-essays.md now includes:
These apply to ALL essay types. Check before any specific rules.
Rule: Every factual claim must be verifiable.
Elaboration: Don't invent dates, statistics, or events. If uncertain, mark for verification. Applicants lose credibility from a single factual error.
Example:
Rule: Every quote must be checked against the original source.
Elaboration: Misquoted professors, misattributed ideas, or paraphrased-as-quoted text damages trust. When in doubt, paraphrase instead of quote.
Example:
Rule: Never fabricate experiences, achievements, or reflections the writer hasn't expressed.
Elaboration: When writer input is needed, use placeholders. The writer must provide: specific research interests, personal reflections, lessons learned, connections between experiences.
Example:
[WRITER: What specific lesson did you take from this experience?
Example style: "I learned to survey literature first—we could have saved weeks"
Your version: _______________]
Rule: Every sentence must relate explicitly to adjacent sentences.
Elaboration: If the connection isn't clear, add transitional language. Readers shouldn't have to infer how ideas connect.
Example:
Rule: Cut phrases that add no meaning.
Elaboration: These phrases signal weak writing and waste word count.
Remove:
Rule: Use active voice unless passive is specifically justified.
Elaboration: Passive voice obscures agency and weakens impact.
Example:
Rule: If a paragraph can become one sentence without losing meaning, compress it.
Elaboration: Verbosity buries ideas. Force radical reduction to find the core.
Example:
When providing essay feedback:
Structure:
Format:
[Issue name]: "[quoted essay text]"
[Single paragraph: problem + suggested fix, 3-5 sentences max]
Priority order:
These signal weak throughlines in ANY essay type:
Response: Push for specificity. What exactly? How specifically?
Use when transcribing audio files with speaker diarization. Triggers on TRANSCRIBE keyword.
Create, update, delete, and query Google Calendar events using gcallm CLI, MCP tools, or direct API calls.
Comprehensive guide for managing Claude Code snippets v2.0 - discovering locations, creating snippets from files, searching by name/pattern/description, and validating configurations. Use this skill when users want to create, search, or manage snippet configurations in their Claude Code environment. Updated for LLM-friendly interface with TTY auto-detection.
Style guide and primer for writing in Warren Zhu's voice. Use when drafting emails, essays, blog posts, technical documents, consulting deliverables, presentations, or any writing for or as Warren. Covers philosophical sensibilities, stylistic patterns, characteristic moves, tone calibration, and professional/technical writing registers. Also useful when understanding Warren's intellectual background and preferences for advising him.
Use when interacting with Harvard Canvas LMS - fetching courses, assignments, grades, submissions, modules, calendar events. Trigger with CANVAS keyword.
Interact with Google Drive API using PyDrive2 for uploading, downloading, searching, and managing files. Use when working with Google Drive operations including file transfers, metadata queries, search operations, folder management, batch operations, and sharing. Authentication is pre-configured at ~/.gdrivelm/. Includes helper scripts for common operations and comprehensive API references. Helper script automatically detects markdown formatting and sets appropriate MIME types.