mcmespinaa
UserClaude Code skill that evaluates a thesis Theoretical Framework chapter against the OL646E (Malmö University SALSU) course rubric. Companion to thesis-anchoring-map.
Categories
Indexed Skills (6)
eval-theories
Evaluate a thesis Theoretical Framework chapter against the OL646E (SALSU Master Thesis) course rubric — the four canonical Theory-Chapter rules (problem-derived selection, selectivity, distinct-from-introduction, closing analytical framework), plus a 12-point pre-submission audit covering critical stance, concept-to-analysis traceability, and chapter-to-chapter coherence. TRIGGER when the user pastes a Chapter 3 / Theory / Theoretical Framework draft, links a markdown or PDF theory chapter, or asks to score, audit, evaluate, critique, or check a theoretical framework. Also trigger on /eval-theories. SKIP when the request is for an introduction (use anchoring-map-evaluator instead), a methodology chapter, a literature review chapter, a findings chapter, or non-thesis writing. Synthesised from the OL646E_2026 course guidelines (Malmö University SALSU programme), Chouliaraki and Fairclough (1999) on theoretical-method integration, and the Nass and Purwin (2024) examination exemplar.
folder-audit
Evaluates any project's folder architecture against the ICM five-layer context hierarchy. Scores Layer 0 (Map/CLAUDE.md), Layer 1 (Rooms/CONTEXT.md), Layer 2 (Stage Contracts), Layer 3 (Reference Material), Layer 4 (Working Artifacts), plus Tools assessment. Checks 14 anti-patterns (8 base + 6 ICM), measures 5 structural metrics. Outputs a graded audit report with prioritized fixes. Use when: setting up Claude Code on a project, reviewing workspace quality, debugging degraded AI output, onboarding a new codebase, scoring folder structure, checking folder quality, evaluating project organization.
pipeline-scaffold
Creates a new ICM pipeline from a domain description. Generates numbered stage folders with CONTEXT.md contracts (Inputs/Process/Outputs), reference and output directories, and a root CONTEXT.md. Use when: setting up a new staged workflow, creating a production pipeline, scaffolding an ICM workspace.
run-stage
Executes a single ICM pipeline stage by reading its CONTEXT.md contract, loading scoped inputs (Layer 3 reference vs Layer 4 working), following the Process section, writing declared outputs, and pausing for human review. Use when: running a pipeline stage, executing a stage, processing the next stage.
stage-review
Reviews a completed pipeline stage before advancing to the next one. Verifies all declared outputs exist, runs the stage's Review Checkpoint criteria, checks quality against the Process intent, and confirms downstream readiness. Use when: reviewing stage output, checking if ready to advance, verifying stage completion.
validate-pipeline
Validates an ICM pipeline's contract chain — checks that each stage's outputs match the next stage's expected inputs, verifies factory/product separation, and flags structural anti-patterns. Use when: checking pipeline integrity, verifying handoffs, debugging broken stage connections.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.