profile-kernel

Manages multi-learner tutor profiles, session slots, roster caps, and level unlock ledgers.

Updated Sep 20, 2026
One-click install
npx skills add https://github.com/alwayslistening86-pixel/claude_plugins --skill profile-kernel-alwayslistening86-pixel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: profile-kernel
Source: https://github.com/alwayslistening86-pixel/claude_plugins/tree/main/generic-tutor-1.2.0/skills/profile-kernel
Command: npx skills add https://github.com/alwayslistening86-pixel/claude_plugins --skill profile-kernel-alwayslistening86-pixel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing multiple learners on one tutoring installation requires strict data isolation, consistent progress tracking, and controlled course enrollment. This Skill provides the profile layer for a tutor system: activating learner sessions, running first-time intake, enforcing roster capacity limits, and maintaining a cumulative level-clearing ledger that gates course access. ## Core Features & Use Cases - Multi-learner profile management: /run <user_id> activates a learner, /add-profile creates new ones, and /profile views or updates the active learner, with each learner isolated in their own /EDU/profile/<user_id>/ folder. - First-ever-load intake flow: When the profile folder is empty, it runs a conversational intake covering education level, preferences, accessibility needs, study availability, and roster capacity before any course is built. - Unlock ledger and roster cap: Owns highest_level_cleared (the single cumulative level-unlock scalar) and roster.max_incomplete_courses, which gate what courses a learner can add next. - Consent-aware persistence: Supports granted, limited, and revoked consent statuses that control exactly which fields persist to disk at session end. - Use Case: A parent sets up tutoring for two children on one machine. Each child gets an isolated profile folder, their own progress files per course, and an independent roster cap, with no cross-learner data bleed. ## Quick Start Ask the AI to run a learner profile by saying: run the profile for user Alex and show their current progress and roster occupancy.

Frequently Asked Questions about profile-kernel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I activate a learner profile in a multi-user tutoring system?▼

Use /run <user_id> to load that learner's folder as active for the session. It advances the session-slot counter once via slot_advance.py and confirms the profile is running; if no match exists, it suggests /add-profile instead of guessing.

How does learner data isolation work between multiple profiles?▼

Each learner gets a private /EDU/profile/<user_id>/ folder containing their student_profile.json and per-course progress files. Sessions may only read or write within the active learner's folder; shared course content is read-only for teaching sessions.

What happens on first-ever load when no profiles exist?▼

The system skips /run, confirms folder access for /EDU/profile/, runs a conversational intake covering education level, preferences, accessibility, availability, and roster capacity, then prompts for subjects via /add-course and finishes with /plan.

Can a learner exceed their roster capacity for incomplete courses?▼

No. roster.max_incomplete_courses is a hard cap checked before any new course is added. Adding beyond it requires completing or dropping an existing course first, though the cap itself can be adjusted later via /profile.

Does the system accept prior qualifications to unlock higher-level courses?▼

No. The highest_level_cleared ledger only increases when every course at a level reaches genuine complete status within the system. Attestation of external prior credit is never accepted as a substitute for clearing levels through actual study.

What data persists when consent is set to limited or revoked?▼

With limited consent, only syllabus_status, current_stage, current_phase, and scheduling bookkeeping persist; softer signals are discarded at session end. With revoked consent, nothing is written to any profile or subject file for that session.