Token导航 LogoToken导航TokenDH.com
开发需要联网github未标认证来源可访问许可证需确认审计通过

hackathon-test-generator黑客马拉松测试生成器

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

326

周安装

14

GitHub Stars

1

下载量

114
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:hackathon-test-generator(黑客马拉松测试生成器)
来源仓库:https://github.com/bernieweb3/hackathon-ai-devkit
仓库路径:skills/hackathon-test-generator
安装命令:
npx skills add https://github.com/bernieweb3/hackathon-ai-devkit --skill hackathon-test-generator
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/bernieweb3/hackathon-ai-devkit --skill hackathon-test-generator

简介

用于辅助测试设计、用例整理和回归验证,支持单元测试与端到端测试编写。

  • 适合让 Agent 根据失败日志定位问题或生成测试计划,提升代码质量。
  • 使用时需确认测试框架、运行命令和夹具数据,避免为通过测试而破坏逻辑。
  • 安装方式:通过 GitHub 仓库安装,命令为 npx skills add https://github.com/bernieweb3/hackathon-ai-devkit --skill hackathon-test-generator。
  • 注意:涉及浏览器或外部服务时,应区分本地模拟与生产环境,防止误操作。

SKILL.md

hackathon-test-generator

Goal

Generate a focused set of test cases and a lightweight test coverage plan that validates the demo flow without requiring full test suite completeness.


Trigger Conditions

Use this skill when:

  • Core MVP features have been implemented and the demo flow is connected end-to-end
  • Done criteria from hackathon-code-implementer are available
  • The team needs to verify the demo will not crash before judging
  • Manual verification steps are needed for a quick pre-demo sanity check
  • Invoked once after the implementation phase stabilizes; re-invoke after any demo-path bug fix

Inputs

InputTypeRequiredDescription
mvp_featuresstring[]YesMVP features from hackathon-scope-cutter
mvp_demo_flowobject[]YesDemo flow steps from hackathon-scope-cutter
tech_stackstring[]YesTechnologies in use
done_criteriastring[]YesDone criteria from hackathon-code-implementer
time_budget_hoursnumberYesHours available for testing

Outputs

OutputDescription
test_casesPrioritized test cases covering the demo flow
coverage_planWhat is tested vs. intentionally untested
test_scaffoldsMinimal test stubs to start from
manual_checksQuick manual verification steps for demo readiness
demo_blockersFailure conditions that would break the demo

Rules

  1. Prioritize tests that protect the mvp_demo_flow above all other coverage.
  2. Generate at minimum one test per done_criterion.
  3. Mark any test not critical to the demo as [NICE-TO-HAVE].
  4. Include at least one negative/edge case test per MVP feature.
  5. test_scaffolds must use the testing framework standard for the primary tech_stack language.
  6. manual_checks must be completable in under 5 minutes total.
  7. Any scenario that would cause a live demo failure must appear in demo_blockers.

Output Format

test_cases:
  - id: "TC-<number>"
    feature: "<feature name>"
    description: "<what is tested>"
    type: "<unit|integration|e2e|manual>"
    priority: "<critical|high|[NICE-TO-HAVE]>"
    input: "<test input>"
    expected_output: "<expected result>"

coverage_plan:
  covered:
    - "<area>"
  intentionally_skipped:
    - area: "<area>"
      reason: "<why skipped>"

test_scaffolds:
  - label: "<test name>"
    language: "<language>"
    snippet: |
      <code>

manual_checks:
  - step: <number>
    action: "<what to do>"
    pass_condition: "<what success looks like>"

demo_blockers:
  - scenario: "<failure scenario>"
    mitigation: "<how to prevent or recover>"

Example

Input:

mvp_features: ["GPT-4 check-in conversation", "Session memory", "Crisis escalation (mocked)"]
mvp_demo_flow:
  - step: 2
    action: "User describes recurring work stress"
    outcome: "AI references last week's similar conversation from memory"
  - step: 3
    action: "User expresses hopelessness"
    outcome: "AI surfaces crisis resource card"
tech_stack: ["Python", "FastAPI", "React", "Redis"]
done_criteria:
  - "New chat session shows AI referencing previous session content"
  - "Redis key contains non-empty summary after session ends"
time_budget_hours: 2

Output:

test_cases:
  - id: "TC-01"
    feature: "Session memory"
    description: "AI references prior session context in a new session"
    type: "e2e"
    priority: "critical"
    input: "Start session 1, say 'I'm anxious about exams'. End session. Start session 2."
    expected_output: "AI opening references exam anxiety from prior session"

  - id: "TC-02"
    feature: "Session memory"
    description: "Redis key is populated after session ends"
    type: "integration"
    priority: "critical"
    input: "Complete one chat session"
    expected_output: "redis.get('user:demo:summary') returns non-empty string"

  - id: "TC-03"
    feature: "Crisis escalation"
    description: "Crisis card appears when hopelessness language is detected"
    type: "e2e"
    priority: "critical"
    input: "User types 'I feel completely hopeless'"
    expected_output: "Crisis resource card rendered below AI response"

  - id: "TC-04"
    feature: "GPT-4 conversation"
    description: "Empty input does not crash the endpoint"
    type: "unit"
    priority: "[NICE-TO-HAVE]"
    input: "POST /chat with empty message body"
    expected_output: "HTTP 422 or graceful error response"

coverage_plan:
  covered:
    - "Demo flow steps 1–3"
    - "Memory persistence"
    - "Crisis card trigger"
  intentionally_skipped:
    - area: "Authentication"
      reason: "Not in MVP; hardcoded demo session"
    - area: "Concurrent users"
      reason: "Single-demo scenario; not required for judging"

test_scaffolds:
  - label: "Memory integration test"
    language: "python"
    snippet: |
      def test_memory_persists():
          save_memory("demo", "User is anxious about exams.")
          assert get_memory("demo") == "User is anxious about exams."

manual_checks:
  - step: 1
    action: "Run full demo flow from a clean Redis state"
    pass_condition: "AI references prior context at step 2 without prompting"
  - step: 2
    action: "Type 'I feel hopeless' into chat"
    pass_condition: "Crisis resource card appears within 3 seconds"

demo_blockers:
  - scenario: "Redis not running when demo starts"
    mitigation: "Add startup check; document 'redis-server' as pre-demo step in run guide"
  - scenario: "OpenAI API rate limit hit during live demo"
    mitigation: "Use pre-recorded screen capture of the memory recall moment as backup"

Context Files

Knowledge Base

  • knowledge/hackathon-demo-patterns.md
  • knowledge/hackathon-common-failures.md
  • knowledge/hackathon-mvp-strategy.md

Playbooks

  • playbooks/hackathon-workflow.md

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

34.18%
按下载量换算39

Claude

30.42%
按下载量换算35

Cursor

16.42%
按下载量换算19

Gemini CLI

9.23%
按下载量换算11

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills