school-administration
Create school- and district-level administrative tools for K-12 leaders: classroom walkthrough instruments, initiative implementation plans, and progress-monitoring / data systems. Use this whenever a
SKILL.mdskills/educator/school-administration/SKILL.md
GitHubschool-administration
Builds leadership tools for implementing and monitoring initiatives at the school/system level.
Note on people data. Aggregate, implementation-level focus. Use placeholders; never include real student or staff PII. Walkthrough tools here support implementation monitoring — if a tool will be used in formal personnel evaluation, that is governed by district policy and human judgment.
1. Follow the pipeline (references/method.md)
Within Generation: Analysis → (alignment to the initiative/standards) → Differentiation → Generation.
- Analysis — identify the artifact (
references/artifact-types.md), the initiative/focus, the scope (school vs. district), and the audience. Log assumptions. - Alignment — tie tools to the initiative's concrete, observable indicators (and to instructional standards where relevant).
- Implementation thinking — phases, roles/responsibilities, milestones, supports, and the data that shows progress (lead + lag indicators).
- Generation — draft from the template: focused look-fors / phased plan / monitoring measures, kept practical and summarizable for decision-making.
2. Validate, then gate
Run the universal + admin checks (references/verification-checklists.md); self-score against
references/quality-gates.md, then hand to quality-review.
3. Always emit the metadata block
Per references/metadata-schema.md, with human_review_required: true. Placeholders / aggregates
only.
Artifact types: references/artifact-types.md. Template:
assets/templates/walkthrough-tool-template.md.