ai-champions
Read Simon's latest AI Champions weekly task from
- License 许可
- MIT
- 最近更新
- 2026-10-28
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ai-champions
- description
- Read Simon's latest AI Champions weekly task from
03 SKILL.md 正文
ai-champions
You are running the /ai-champions workflow. Find this week's brief from Simon, implement it, and post one clean submission to #ai-champions.
Step 1 — Find Simon's Latest Task
Read the #ai-champions channel (ID: C0AJ3CLSGBX):
Use mcp_hub_slack__conversations_history with channel_id="C0AJ3CLSGBX" and limit=30.
Find the most recent message from simon.chapman (user ID: U08HE2KV4SX) that is a weekly brief. Characteristics:
- Contains "AI Champions Week X Brief" or "Brief:" in the text
- Has numbered submission requirements (1. 2. 3. etc.)
- Is NOT the nudge bot ("AI CHAMPIONS NUDGE")
- Is NOT a results/winner announcement
Extract: week number, the core challenge, and the numbered submission requirements.
Tell the user what the task is and ask if they want to proceed.
Step 2 — Implement the Task
Work to implement whatever the brief asks for. The approach depends on that week's challenge.
Use appropriate agents and tools. Plan → execute → verify.
Ask the user for input when:
- The approach requires a design decision you can't resolve alone
- Mid-way validation is needed
- You're unsure what counts as "done" for this task
Keep implementation focused — deliver exactly what the brief asks for, no more.
Step 3 — Compose the Slack Submission
Write ONE message. Rules:
- Succinct — short paragraphs or bullets, no waffle
- Human — write like a person, not a bot report
- Addresses the numbered requirements from Simon's brief, in order
- Honest — if something didn't work perfectly, say so briefly
- No emoji overload, no corporate tone, no "In conclusion..."
- Max ~300 words
Format:
*Week X — [Brief title]*
[2–3 sentence summary of what you built/did]
1. [requirement 1 answer — 1–2 sentences]
2. [requirement 2 answer — 1–2 sentences]
3. [requirement 3 answer — 1–2 sentences]
...
[Optional: one honest closing line about whether you'd trust it/use it again]
Step 4 — Confirm with User, Then Post
Show the draft to the user. Ask: "Happy for me to post this?"
Once confirmed, post exactly one message:
mcp_hub_slack__conversations_add_message(
channel_id="C0AJ3CLSGBX",
content_type="text/markdown",
text="<your write-up>"
)
Confirm to the user it was sent and show the message timestamp.
04 同仓库更多 Skills
terraform-test
Comprehensive guide for writing and running Terraform tests. Use when creating test files (.tftest.hcl), writing test scenarios with run blocks, validating infrastructure behavior with assertions, mocking providers and data sources, testing module outputs and resource configurations, or troubleshooting Terraform test syntax and execution.
terraform-style-guide
Generate Terraform HCL code following HashiCorp's official style conventions and best practices. Use when writing, reviewing, or generating Terraform configurations.
terraform-stacks
Comprehensive guide for working with HashiCorp Terraform Stacks. Use when creating, modifying, or validating Terraform Stack configurations (.tfcomponent.hcl, .tfdeploy.hcl files), working with stack components and deployments from local modules, public registry, or private registry sources, managing multi-region or multi-environment infrastructure, or troubleshooting Terraform Stacks syntax and structure.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.
run-acceptance-tests
Guide for running acceptance tests for a Terraform provider. Use this when asked to run an acceptance test or to run a test with the prefix `TestAcc`.
refactor-module
Transform monolithic Terraform configurations into reusable, maintainable modules following HashiCorp's module design principles and community best practices.