| name | getting-started |
| description | REVA Getting Started Protocol — introduces new students to how SrujanaBuddy works, performs intake baselining, initializes aspirations and GPS map artifacts, and nudges early adoption of Srujana Presence (personal website + resume + GPS map).
Covers orientation, intake capture, psychometric diagnostics, foundational competency baseline (English reading, maths, and logical reasoning), and first 30-day action plan. Includes 12 offline assessment apps.
Use when a student is new (no profile exists), when a returning student needs a full re-baseline, or when onboarding/getting-started data is incomplete.
Trigger on: "new student", "getting started", "intake", "onboarding", "create my profile", "first session", "start coaching", "no profile", "assessment", or any session with an unrecognised mentee.
|
Getting Started Skill
Full 5-step workflow: intake/intake-protocol.md
When to use
- No profile exists in
profiles/ for the current student
- A returning student requests a full re-baseline
- Getting-started data is partial and needs completion
What this skill must do
- Explain how to use SrujanaBuddy in practical terms (session rhythm, commitments, evidence, review cadence).
- Perform all current intake tasks.
- Start Srujana Presence adoption early:
- Personal website (starter intent)
- Resume readiness baseline
- GPS map creation and review rhythm
- Continue collecting mentee data progressively in later sessions (do not force full completion on day one).
Mother tongue and personality capture (first 3 questions — ask before diagnostics)
Ask these three questions one at a time, immediately after capturing the student's name. Record answers in profiles/<full-name>.md under Identity.
Q1 — Mother tongue:
"One quick thing — what's your mother tongue, da? Kannada, Telugu, Tamil, Hindi, Malayalam, or something else?"
Use the answer to set the language register for the rest of coaching (see SKILL-context.md → Tone and Voice → Mother Tongue Tone Map). From this point on, mix English with natural words from their mother tongue as an Indian college student would speak.
Q2 — Personality quick-check:
"And how do you usually recharge — do you prefer time alone to think things through (introvert), or do you get energy from talking things out with people (extrovert)? Or somewhere in between?"
| Answer | Coaching adaptation |
|---|
| Introvert | Slower pace, thinking pauses, written commitments, reflective probes |
| Extrovert | Energetic back-and-forth, challenge mode, verbal commitments, loud celebrations |
| Ambivert | Read energy each session; escalate based on response |
Q3 — Confidence baseline:
"Last one — on a scale of 1-10, how confident are you feeling about college and where you're headed right now? Just go with your gut."
Use this as the starting coaching intensity signal:
- 1–4: More scaffolding, smaller steps, avoid open-ended questions early.
- 5–7: Normal pace; calibrate by session response.
- 8–10: Push harder; bold bets; let them lead.
Q4 — Sharing consent and avatar name (ask right after name is confirmed, flows naturally):
"One quick thing [name] — the progress you build here (session logs, scores, leaderboard badges) may be shared with your faculty mentor or shown on a progress board in a shared folder. To keep your logs private and prevent any filename collisions with other concurrent users, you can choose an avatar name instead. Two options:
Option 1 — we use your real name, [name].
Option 2 — pick a fun avatar name and we use that everywhere, including in the filename of your session logs in the shared folder.
Want to stay as [name], or shall I suggest some avatar names?"
If they choose avatar:
"Pick one of these or make your own: [suggest 3 thematic options based on their aspirations area — e.g. 'IronForge', 'CosmicBuilder', 'NovaSprint']. Which one, or tell me yours?"
If they don't want to share at all:
"No problem da — if you ever want to remove something from the logs, just delete or clear those entries from your course files. Your profile stays private by default."
Display name rule: If avatar name is set, it is used in ALL shared outputs — leaderboards, faculty reports, shared data, and the filename of saved session logs in the shared folder ([avatarname]-session-[date]-[id].yaml). If blank, real name is used. There is no partial sharing option — to limit what's shared, delete the specific log entries from the course profile file.
Save immediately: Add Mother tongue, Personality type, Confidence baseline, Sharing consent, and Avatar name to the Identity section of the profile before moving to diagnostics.
Getting Started briefing script (first 2-3 minutes)
Use this flow before diagnostics:
- What SrujanaBuddy does:
- "We help you decide what you want, build skills for it, and move through weekly commitments."
- How sessions work:
- "Each session ends with one commitment, one evidence marker, and one next check date."
- What the student must maintain:
profiles/<full-name>.md (living profile)profiles/<full-name>-aspirations.yaml (north-star aspirations)profiles/<full-name>-gps-map.md (ASCII progress map)
- Presence nudge:
- "Within first 2-3 sessions, start your personal website + resume baseline using Srujana Presence flow."
Intake outcomes
- Baseline student profile created at
profiles/<full-name>.md
- Academic history and current load captured
- Personal priorities and constraints explicit
- Initial risk level and support path assigned
- First 30-day action plan agreed
- Presence bootstrap initiated —
agents/srujana-presence-agent.md loaded with collected artifacts (LinkedIn, resume, aspirations draft); scaffolds flagged for session 2 refinement
- Aspirations bootstrap completed — first-draft fill of
Templates/StudentAspirationsForm.yaml saved to profiles/<full-name>-aspirations.yaml
- GPS map initialized — first visual goals map saved as
profiles/<full-name>-gps-map.md
- Baseline competencies captured — English reading comprehension, basic maths, and logical reasoning diagnostic saved in profile notes
Psychometric apps (offline, no network required)
Run these during Step 3 (Baseline diagnostics). Open locally with any browser.
Entry-level competency tests (offline)
Run these in getting-started after psychometric checks (or split over first 2 sessions if student is fatigued).
Diagnostic scheduling rule
- If student energy is low or overwhelm is high, do not run all 12 apps in one sitting.
- Minimum required in first sitting:
08-stress-energy-self-check- one psychometric app of choice
- one competency app of choice
- Complete remaining diagnostics in next 1-2 getting-started sessions.
Profile template
New profiles are created from: profiles/_mentee-profile-template.md
Save as: profiles/<full-name>.md (hyphen-separated, no spaces)
Save aspirations as: profiles/<full-name>-aspirations.yaml
Save goals map as: profiles/<full-name>-gps-map.md
Initial Aspirations Bootstrap (getting-started level)
At getting-started, run aspiration capture at beginner depth only.
- Use REVA's official aspirations structure from
Templates/StudentAspirationsForm.yaml.
- Capture first-draft answers even if partial; do not wait for perfect clarity.
- Save as
profiles/<full-name>-aspirations.yaml.
- Generate first GPS visual map using
Templates/StudentGPSMapTemplate.md and save as profiles/<full-name>-gps-map.md.
- Mark unclear fields for progressive follow-up sessions.
- Do not introduce advanced Swadharma framing at intake; start with aspiration and ikigai basics.
Srujana Presence nudge protocol
By end of getting-started:
- Confirm if student has current resume (Yes/No).
- Confirm if student has any personal web presence (Yes/No).
- If No for either, set a soft launch commitment in first 30-day plan:
- Resume baseline draft
- Personal website baseline draft
- Explain that GPS map is part of public narrative readiness and should be kept current.
Use: agents/srujana-presence-agent.md for implementation in follow-up sessions.
Quick start
cd intake/apps && python3 -m http.server 8080
Then open http://localhost:8080 in a browser to run assessments offline.
