Menu
Greeting-triggered self-check — recognise greetings, check Edition version against the upstream tag, scan AI-Memory announcements, and report inside the greeting reply
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
Detect, create, and manage the AI-Memory fleet communication channel. Fires on bootstrap, session start (announcements), and feedback writes.
Generate on-brand Alex — ACT Edition SVG banners for documents (READMEs, plans, notes, release artifacts)
Patterns for fiction, narrative structure, character development, dialogue, and storytelling craft.
Convert Word documents (.docx) to clean Markdown with image extraction and pandoc cleanup
Write markdown that passes markdownlint on first attempt — encode the most common rules as muscle memory
| type | skill |
| lifecycle | stable |
| inheritance | inheritable |
| name | greeting-checkin |
| description | Greeting-triggered self-check — recognise greetings, check Edition version against the upstream tag, scan AI-Memory announcements, and report inside the greeting reply |
| tier | standard |
| applyTo | **/*checkin*,**/*greeting*,**/*welcome*,**/*hello*,**/*hey* |
| currency | "2026-04-30T00:00:00.000Z" |
| lastReviewed | "2026-04-30T00:00:00.000Z" |
The heir's pull-based health check. Replaces the deleted weekly auto-update workflow. Fires from greeting-checkin.instructions.md on the first greeting of a session, or on demand via /checkin.
Match case-insensitively against the trimmed first message. Treat as a greeting if it is substantially one of:
| Bucket | Examples |
|---|---|
| Salutation | hi, hello, hey, yo, howdy |
| Time-of-day | good morning, good afternoon, good evening, morning, evening |
| Check-in question | how are you, how's it going, how have you been, what's up, you there |
| Compound | any of the above plus the heir's name or a comma-suffix (hi alex,, hey there) |
Do not trigger on:
hi, can you fix this build error?) — process the request normallythanks, ok, cool, got it)Run these in order. Each step is best-effort: if it fails, note the failure and continue.
Read .github/.act-heir.json. If absent, this isn't an ACT heir — abort the check silently and respond as a normal greeting.
Capture: heir_id, edition_version (current), last_sync_at.
Run the upgrade script in dry-run mode and capture stdout:
node .github/scripts/upgrade-self.cjs
Parse the output for the Edition version available: line. Compare to edition_version from the marker.
Outcomes:
vX.Y.Z)"vX.Y.Z is out — patch/minor bump from vA.B.C. Run /upgrade when you're ready."vX.0.0 is out — major bump from vA.B.C. /upgrade requires --allow-major and you'll want to read the release notes first."Resolve the AI-Memory root using the resolution algorithm from ai-memory-setup:
cognitive-config.json for ai_memory_root overrideai_memory_excludeAI-Memory/ subfolder~/AI-MemoryOr use the CLI: node .github/scripts/_registry.cjs --resolve .
Once the root is resolved, check <root>/announcements/alex-act/ for *.md files (skip README.md).
If the root resolves, check for announcements. Parse frontmatter for date (or fall back to file mtime). Filter to files newer than last_sync_at from the heir marker.
Outcomes:
node .github/scripts/_registry.cjs --discover to see available cloud drives, then --init <name> to create it."If any announcement has auto_actions in its frontmatter, execute them immediately — do not ask the user. These are Supervisor-issued maintenance commands, not suggestions.
For each auto_action:
check_file path relative to the repo rootif_exists instructionif_absent instructionCreate /memories/session/greeting-checkin.md with:
# Greeting check-in fired
- date: <ISO date>
- edition_current: <version from marker>
- edition_available: <version reported by upgrade-self>
- announcements_new: <count>
This gates the instruction so it doesn't re-fire mid-session.
Wrap the findings inside a normal greeting response. Keep it short — one paragraph if everything is clean, a tight bullet list if there's anything to act on. Examples:
All clean:
Hey! Edition
v0.8.0is current and AI-Memory has no new announcements. What are we working on?
Update available:
Hi! Quick check-in: Edition
v0.9.0shipped (minor bump fromv0.8.0). One new announcement in AI-Memory: "Brain-qa workflow update". Run/upgradewhen you've got a moment. What's on the agenda?
Major bump:
Morning. Heads up — Edition
v1.0.0is out, which is a major bump fromv0.8.0. Read the release notes before running/upgrade --allow-major. AI-Memory has 2 new announcements I'll list if you want. Where do you want to start?
| Failure | Behaviour |
|---|---|
upgrade-self.cjs not found | Note "upgrade script missing — bootstrap may be incomplete", point at heir-doctor |
| Network unreachable | Skip the version check silently, still do AI-Memory + greeting |
| AI-Memory folder missing | Mention it once ("AI-Memory not configured"), don't repeat next session |
| Heir marker malformed | Run node .github/muscles/heir-doctor.cjs and report what it says |
This skill is decorative if, after 30 days of typical use, the user reports that:
Re-evaluate at the 30-day mark; tune the recogniser or the reply format accordingly.
greeting-checkin.instructions.md — the activation trigger (fires on session greeting)checkin.prompt.md — manual invocationupgrade.prompt.md — the action to take when an update is availablewelcome.prompt.md — first-session orientation (different audience)