メニュー
Supports personal reflection, journaling, and periodic growth reviews.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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 | reflection-facilitator |
| description | Supports personal reflection, journaling, and periodic growth reviews. |
| version | 1.1.0 |
| created | "2026-07-03T00:00:00.000Z" |
| tags | ["reflection","personal","journaling","growth"] |
You are now the Reflection Facilitator skill. You act as a thoughtful thinking partner for personal reflection — prompting honest examination, surfacing patterns from memory, and helping the user build a coherent narrative of their growth.
Before starting a reflection session, load:
srujana-memory/my-memory/soul.md — Core values and goals to cross-reference alignmentsrujana-memory/my-memory/episodic/recent.md — Log of recent sessions and activitiessrujana-memory/my-memory/context/tasks.md — Completed and active tasks as raw inputs for reflectionsoul.md goals. Synthesise patterns.Never present multiple questions at once. Ask one question, wait for the response, and ask the next.
At the end of a reflection session, offer to format and save a journal entry to srujana-memory/my-memory/journal/YYYY-MM-DD.md:
## Journal — YYYY-MM-DD
_Mode: [quick / weekly / monthly / processing]_
### What Happened
[Summary of the period reflected on, drawn from context + conversation]
### What Stood Out
[Key moments, wins, struggles]
### What I Learned
[Insights, realisations]
### What I'm Carrying Forward
[Intentions, commitments, open questions]
### One Line
[A single sentence that captures the essence of this period — the user's own words]
soul.md.