Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
winstonkoh87 avatar

Academic Delivery

  • 4 installs
  • 553 repo stars
  • Updated August 5, 2026
  • winstonkoh87/athena-public

Helps with ai & agent building tasks.

About

academic-delivery is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • academic-delivery
  • AI & Agent Building
  • AI-coding skill

Academic Delivery by the numbers

  • 4 all-time installs (skills.sh)
  • Ranked #13,372 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/winstonkoh87/athena-public --skill academic-delivery

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs4
repo stars553
Last updatedAugust 5, 2026
Repositorywinstonkoh87/athena-public

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Academic Delivery Skill

Purpose: Structured pipeline for academic/knowledge deliverables. Prevents the V1-is-weak failure mode by auto-triggering adversarial review.
Origin: Extracted from real-world execution of Assignments 11–15 (Mar 2026). Every assignment manually reconstructed this pipeline — now it's codified.

The 8-Step Pipeline

Step 1: INTAKE

  • Parse brief/requirements document
  • Extract: word count, format (essay/report/problem set), rubric criteria, deadline, client name
  • Identify prescribed frameworks or sources (e.g., "use Hirshfield as critical lens")
  • Log to .context/client_work/pricing_log.md if commercial

Step 2: SCOPE

  • Classify deliverable type:
  • Essay (argumentative, comparative, reflective)
  • Report (technical, research, capstone)
  • Problem Set (calculations, code, SPSS)
  • Presentation (slides, pitch deck)
  • Estimate complexity (Λ score)
  • If commercial: trigger client-pricing skill for quote generation

Step 3: RESEARCH

  • Load domain context via Exocortex (smart_search.py)
  • If external research needed: trigger deep-research-loop (Cluster #12)
  • Extract key frameworks, models, citations
  • Build a reference spine (3–7 sources minimum for essays)

Step 4: DRAFT (V1)

  • Write full first draft to spec
  • Embed citations inline
  • Target 90–95% of word count (leave room for red-team additions)
  • DO NOT deliver V1. V1 is always a working draft, never the output.

Step 5: RED-TEAM (Mandatory — Auto-Triggered)

[!IMPORTANT]
This step is non-negotiable. It fires automatically after Step 4. The Assignment 13 V1 failure (zero counter-readings, zero formal analysis) is the canonical case study for why.
  • Feed V1 through adversarial review (Cluster #8 — red-team-review)
  • Evaluate against:

1. Counter-reading: Does the draft contain at least one steelmanned opposing interpretation + rebuttal? (~80 words, non-negotiable) 2. Formal analysis: For literary/theoretical work — does it engage with the form (enjambment, structure, methodology), not just content? 3. Evidence density: Every claim backed by textual evidence or citation? 4. Rubric alignment: Does the draft hit every criterion in the brief? 5. Genre compliance: Is the output in the correct academic register? (MLA vs APA vs report format)

  • Generate a fix list with accept/reject decisions for each criticism
  • Reject invalid criticisms (category errors, phantom rubric scoring, n=1 methodology applied to literary analysis)

Step 6: REVISE (V2+)

  • Incorporate accepted fixes from red-team
  • If >3 structural issues found, produce V3 (rare — V2 is usually sufficient)
  • Re-check word count against target
  • Verify counter-reading and formal analysis are present

Step 7: COMPILE

  • Format per submission requirements:
  • Cover page (if required)
  • Table of Contents (forces a structural audit — per Session 06 learning)
  • Section headers (topic-based, not numbered, for MLA essays)
  • Works Cited / References (MLA, APA, or Harvard as specified)
  • Appendices (if applicable)
  • Compaction triage: If over word count, cut from infrastructure (setup/transition/repetition) first, analytical core last. Ratio: 70% infrastructure cuts, 30% analysis cuts.
  • Paragraphing pass — wall-of-text paragraphs are a delivery failure, not a content failure.

Step 8: DELIVER

  • Final proofread (grammar, citation format, page numbers)
  • Export to required format (Markdown → Google Doc → DOCX)
  • If commercial: send to client with scope confirmation
  • Log completion to activeContext / quicksave

Exit Gate

No deliverable leaves Step 8 without:

  • [x] Counter-reading present (if argumentative/analytical)
  • [x] Formal analysis present (if literary/theoretical)
  • [x] Word count within ±5% of target
  • [x] All rubric criteria addressed
  • [x] Format compliant (citations, headers, cover page)

Reflexion Archive

[REFLEXION] What failed: Assignment 13 V1 shipped with zero counter-readings and zero formal analysis. Why: Over-optimised for clean thesis confirmation. Lesson: Auto-trigger red-team after V1. 80 words for a counter-reading is non-negotiable.
[REFLEXION] What failed: Assignment 15 capstone at $500/6hrs = $83/hr (73% rate collapse). Why: No pricing skill fired during intake. Lesson: Step 2 (SCOPE) must trigger pricing evaluation for commercial work.

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.