From kubecon-cfp
<!-- justify: CF-side-effect Edit/Write fix detected issues in SKILL.md with user approval -->
npx claudepluginhub smykla-skalski/sai --plugin kubecon-cfpThis skill uses the workspace's default tool permissions.
<!-- justify: CF-side-effect Edit/Write fix detected issues in SKILL.md with user approval -->
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Craft a high-quality KubeCon CFP submission using data-driven insights from 1,100+ accepted talks and official reviewer criteria.
Parse from $ARGUMENTS:
Read reference files before starting:
Read: references/cfp-criteria.md — scoring dimensions, character limits, format rules
Read: references/talk-patterns.md — title patterns, topic trends, acceptance data
Evaluate the user's topic idea against acceptance data:
Output a brief assessment with recommended track, competitiveness estimate, differentiation angles, and similar accepted talk titles.
Use AskUserQuestion to gather concrete details:
Wait for concrete answers before proceeding because vague submissions get rejected.
Generate 5 title options using proven patterns from references/talk-patterns.md. Re-read the title patterns section before generating.
Rules: title case, under 75 characters (hard limit), specific over generic, include scale/numbers when possible, no vendor/product names unless open-source project.
Present options ranked by likely reviewer impact. Let user pick or iterate via AskUserQuestion.
<example> Topic: "We migrated our API gateways from Kong to Gateway API across 200 microservices" Track: ConnectivityTitle options:
Adapt title style to --format: lightning talks need punchier/shorter titles, tutorials should signal hands-on content.
Structure: Hook → Promise → Payoff
Rules: third person ("The speaker will..." not "I will..."), complete sentences (gets published on the schedule), specific numbers and metrics, no marketing/sales language, no jargon without context, first sentence must hook — reviewers read 100-200 proposals.
Show character count after writing. Must be ≤1,300.
<example> Input: Gateway API migration, 200 services, zero downtime, 6-month timelineAbstract (847 chars): "Managing API traffic across 200 microservices through a proprietary gateway created vendor lock-in, limited extensibility, and cost $2M annually in licensing. This talk presents a six-month migration to Kubernetes Gateway API that achieved zero downtime while serving 50K requests per second. The speaker will walk through the three-phase migration strategy: shadow traffic validation, canary rollout per service tier, and automated rollback triggers that caught 12 configuration errors before they reached production. Attendees will learn a concrete migration playbook applicable to any gateway transition, specific pitfalls around HTTPRoute weight distribution at scale, and how to build confidence metrics that let teams migrate without fear." Character count: 847/1,300 </example>
This is a separate section visible only to reviewers — not a copy of the abstract.
Cover: who benefits (specific personas), how this advances the ecosystem (open-source contributions, shared learnings), why now (timeliness), what gap this fills in current conference content.
Show character count after writing. Must be 1,000-1,500.
Help the user identify and format supplemental materials: previous talk recordings (strongest signal), blog posts, GitHub repos, LinkedIn profile, published articles.
If user has no materials, suggest creating a blog post or recording a practice talk before submitting.
Score the submission against the 4 official criteria from references/cfp-criteria.md (1-5 scale): Content, Originality, Relevance, Speaker(s).
Run the pre-submit checklist from references/cfp-criteria.md and flag issues.
<example> Input: --review on a draft titled "Introduction to Service Mesh"Review output:
Flags: title too generic (fails "scroll past" test), no end-user signal, steady/declining topic needs sharp angle. Recommend pivoting to a specific migration story or failure case. </example>
If user wants extra insight, spawn a research agent to search for similar KubeCon talks, identify how the angle differs, and find gaps in existing coverage.
Read references/output-template.md for the submission format. Save to ${XDG_DATA_HOME:-$HOME/.local/share}/sai/kubecon-cfp/submissions/[title-slugified].md.
Not designed for non-CNCF conferences (DevOpsDays, QCon, re:Invent). The acceptance data, scoring criteria, and track structure are KubeCon/CloudNativeCon-specific.
# Basic topic
/kubecon-cfp "API gateway migration to Gateway API at scale"
# With track and format
/kubecon-cfp "eBPF-based network policies" --track Security --format lightning
# Review an existing draft
/kubecon-cfp --review
# Tutorial format
/kubecon-cfp "hands-on Cilium service mesh" --track Connectivity --format tutorial