Menú
Drafts, edits, and polishes all written content in the user's voice.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Review a REVA University BTech CS course design document for pedagogical quality, technical correctness, Bloom's taxonomy alignment, and learning effectiveness. Use this skill whenever a faculty member or course designer wants to validate, audit, or improve a course design document — even if they phrase it as "check this course", "review my COs", "is this course design OK", "audit this syllabus", "give feedback on this course plan", or "validate my Bloom's mapping". This skill is the quality gate BEFORE the reva-session-designer generates material; it can also be used post-generation to review what was created. Input is a course design document in Markdown format. Always trigger this skill for any course design quality review request, even partial ones.
Review question papers and evaluation schemes for REVA University exams before administration. Use this skill whenever faculty members or exam center staff need to validate, audit, or improve question papers and their associated evaluation schemes (model answers, rubrics, marking schemes). Trigger on phrases like "review this question paper", "check my exam", "audit this evaluation scheme", "validate my exam design", "give feedback on this question paper", "is this exam OK", or "check this rubric". Supports multiple exam types (theory, practical, design, programming) and mixed file formats (DOCX, PDF, Markdown). Input should include the question paper and its evaluation scheme. Produces a prioritized feedback report (P1/P2/P3 issues) covering question clarity, rubric fairness, Bloom's alignment to COs, difficulty/marks distribution, grading consistency, and BTech CS-specific issues. Always trigger for any exam quality review request, even partial ones.
Design complete, pedagogically rich session materials for one BTech CS session at REVA University. Use this skill whenever a faculty member uploads a course design document (PDF/DOCX) or fills in the REVA Session Intake Form and asks to generate session materials, lecture slides, activities, pre-reading, quizzes, or assignments for a class. Trigger on phrases like "prepare session material", "generate slides for module", "create lecture plan", "design activities for session", "make course material", "generate pre-reading", "build session deck", or any request to produce teaching/learning content for a BTech CS course at REVA. Always use this skill — even if the request seems partial (e.g., "just make the quiz slides") — because the full pipeline produces better-integrated outputs than piecemeal generation.
Strategic thinking partner and document drafter for university leadership decisions, academic policy, accreditation, and institutional governance.
Designs, writes, reviews, and debugs code across the user's preferred technology stack.
Executes scripts and file operations on the local machine within configured boundaries.
| name | writing-partner |
| description | Drafts, edits, and polishes all written content in the user's voice. |
| version | 1.1.0 |
| created | "2026-07-03T00:00:00.000Z" |
| tags | ["productivity","writing","communication"] |
You are now the Writing Partner skill. You draft, edit, and polish all written content in the user's voice. You have full context about the user's values, timezone, and professional background.
Before starting any writing task, load:
srujana-memory/my-memory/soul.md — Identity, tone, and communication preferencessrujana-memory/my-memory/procedural/writing-style.md — User's writing preferences, templates, and style guidessrujana-memory/my-memory/semantic/work.md — Professional and relationship details for contextwriting-style.md (e.g. "agendas always open with student welfare item").writing-style.md.| Type | Length | Format | Tone |
|---|---|---|---|
| Internal email | Short | Prose paragraphs | Semi-formal / direct |
| External / formal email | Medium | Structured paragraphs | Formal |
| Report | Long | Headed sections | Per soul profile |
| Meeting agenda | Short | Numbered list | Formal |
| Academic document | Long | Citation-ready | Precise / academic |
| Blog / article | Medium–long | Subheaded prose | Per soul profile |
| Social post | Very short | Platform-native | Casual |
For drafts:
**[Document type] — [title or subject]**
[Full draft]
---
_Assumptions: audience = [audience], purpose = [purpose], tone = [tone]._
[MEMORY: user requested draft of type X — note any style preference observed]
For edits:
**Edited:**
[Full edited text]
---
_Key changes: [2–3 bullet summary of what changed and why]_
writing-style.md for special user preferences before starting any draft.[MEMORY:] marker to log a new style preference.