shared-subject-profile-loader

Load per-subject profiles and export SUBJECT_* environment variables.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AKCqhzdy/dse-subject-grading --skill shared-subject-profile-loader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: shared-subject-profile-loader
Source: https://github.com/AKCqhzdy/dse-subject-grading/tree/main/skills-v3/shared-subject-profile-loader
Command: npx skills add https://github.com/AKCqhzdy/dse-subject-grading --skill shared-subject-profile-loader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill reads per-subject profiles from data/subjects/<subject>/profile.md, validates the frontmatter, and exposes subject-level configuration as environment variables for downstream agents. It also writes the profile body to a reusable notes file for sub-agent prompts and gracefully falls back to neutral defaults when a profile is missing.

Core Features & Use Cases

  • Reads data/subjects/<subject>/profile.md (optional) and loads core fields into environment variables.
  • Validates simple frontmatter (subject, report_language, mark_increment, etc.) and exports corresponding values; writes notes body to SUBJECT_NOTES_PATH for prompts.
  • Supports emitting environment variables or a JSON blob for downstream orchestration.

Quick Start

Use the shared-subject-profile-loader to load the subject profile and export SUBJECT_* env vars for downstream agents.

Frequently Asked Questions about shared-subject-profile-loader

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

FAQPage Schema
How do I load per-subject environment variables for downstream agents?▼

Populate subject-specific env vars by reading data/subjects/<subject>/profile.md, validating its YAML frontmatter, and exporting the fields as SUBJECT_* variables for downstream agents.

What happens if a subject profile is missing when loading env vars?▼

When a subject profile is missing, the loader gracefully falls back to neutral default values, ensuring downstream agents still receive required SUBJECT_* environment variables for execution.

How do I pass subject profile data to an orchestrator as JSON?▼

Pass subject profile data to an orchestrator by configuring the loader to emit a JSON blob, providing the extracted frontmatter fields for structured consumption by orchestrating agents.

Can I use a YAML frontmatter profile to configure subagent prompts?▼

Yes, the loader validates YAML frontmatter fields like report_language and writes the profile body to SUBJECT_NOTES_PATH, providing reusable notes for subagent prompt injection.

Does the shared-subject-profile-loader require any external dependencies?▼

No, the shared-subject-profile-loader operates entirely through internal scripts with zero external dependencies, reading local profile files and exporting environment variables.