mcpField

hackathon-track-analyzer

github.com/bernieweb3Productivity43 installs
Repository

About hackathon-track-analyzer

A skill for hackathon teams that turns track descriptions, sponsor briefs, and judging rubrics into constraints, evaluation criteria, and strategic opportunities. It avoids inventing requirements and can recommend next skills in the workflow.

Key features

  1. 01Extract mandatory and optional constraints
  2. 02Order sponsor priorities
  3. 03Structure evaluation criteria and disqualifiers
  4. 04Identify strategic opportunities
  5. 05Recommend follow-up skills

Use cases

  1. 01Reviewing track requirements before ideation
  2. 02Comparing sponsor prize priorities
  3. 03Planning around a judging rubric
  4. 04Checking conditions that could disqualify a submission

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/bernieweb3/hackathon-ai-devkit --skill hackathon-track-analyzer

After installing, type/hackathon-track-analyzerin Claude Code to confirm it loaded.

Details

From the project README

hackathon-track-analyzer

Goal

Parse hackathon track descriptions, sponsor briefs, and theme statements to extract structured constraints, evaluation criteria, and strategic opportunities.


Trigger Conditions

Use this skill when:

  • A hackathon track description, theme, or event page is available
  • Sponsor briefs or prize track details need to be parsed
  • Judging criteria or a scoring rubric must be structured before ideation begins
  • The team needs to understand disqualifying constraints before committing to an idea
  • This is always the first skill invoked in any hackathon workflow

Inputs

InputTypeRequiredDescription
track_descriptionstringYesRaw text of the hackathon track or theme announcement
sponsor_briefsstring[]NoSponsor challenge briefs or prize track descriptions
judging_rubricstringNoAny published judging criteria or scoring rubric
hackathon_duration_hoursintegerYesTotal hackathon duration in hours

Outputs

OutputDescription
track_summaryOne-sentence summary of the track's core theme
required_constraintsMandatory constraints teams must satisfy
optional_constraintsNice-to-have constraints for bonus scoring
sponsor_prioritiesOrdered list of what each sponsor values most
evaluation_axesScoring dimensions extracted from rubric or inferred
strategic_opportunitiesHigh-leverage angles or underserved areas within the track
disqualifiersConditions that would disqualify a submission
recommended_skillsSuggested devkit skills to invoke next

Rules

  1. Extract only what is explicitly stated or strongly implied; do not fabricate constraints.
  2. Prioritize mandatory constraints over optional ones.
  3. Flag ambiguous language with [AMBIGUOUS] marker.
  4. Map each sponsor's stated priorities to 1–3 concrete actionable requirements.
  5. Identify at least one underexplored strategic opportunity per track.
  6. Output recommended_skills drawn only from the hackathon-ai-devkit skill list.

Output Format

track_summary: "<string>"

required_constraints:
  - "<constraint>"

optional_constraints:
  - "<constraint>"

sponsor_priorities:
  - sponsor: "<name>"
    priorities:
      - "<priority>"

evaluation_axes:
  - axis: "<name>"
    weight: "<high|medium|low>"
    description: "<string>"

strategic_opportunities:
  - "<opportunity>"

disqualifiers:
  - "<condition>"

recommended_skills:
  - "<skill-name>"

Example

Input:

track_description: "Build solutions that use AI to improve mental health outcomes for young adults."
sponsor_briefs:
  - "OpenAI: Best use of GPT-4 API for empathetic user interactions"
judging_rubric: "Innovation (30%), Impact (30%), Technical execution (20%), Presentation (20%)"
hackathon_duration_hours: 24

Output:

track_summary: "Use AI to improve mental health outcomes for young adults."

required_constraints:
  - "Solution must demonstrably address mental health for ages 18–30"

optional_constraints:
  - "Bonus scoring for use of OpenAI GPT-4 API"

sponsor_priorities:
  - sponsor: "OpenAI"
    priorities:
      - "Empathetic, context-aware conversational responses"
      - "Responsible AI usage with safety guardrails"

evaluation_axes:
  - axis: "Innovation"
    weight: "high"
    description: "Novel approach to mental health support beyond generic chatbots"
  - axis: "Impact"
    weight: "high"
    description: "Measurable improvement in user wellbeing or access to resources"

strategic_opportunities:
  - "Underserved: peer-support facilitation rather than direct therapy replacement"

disqualifiers:
  - "Solutions that claim to diagnose or treat clinical conditions"

recommended_skills:
  - "hackathon-problem-space"
  - "hackathon-idea-generator"

Context Files

Knowledge Base
  • ../hackathon-shared-resources/knowledge/hackathon-judging-criteria.md
  • ../hackathon-shared-resources/knowledge/hackathon-winning-patterns.md
  • ../hackathon-shared-resources/knowledge/hackathon-tools.md
  • ../hackathon-shared-resources/knowledge/hackathon-common-failures.md
Playbooks
  • ../hackathon-shared-resources/playbooks/hackathon-workflow.md
  • ../hackathon-shared-resources/playbooks/24h-hackathon-playbook.md
  • ../hackathon-shared-resources/playbooks/36h-hackathon-playbook.md
  • ../hackathon-shared-resources/playbooks/48h-hackathon-playbook.md

Comments

Markdown supported