菜单
A specialized workflow for crafting high-quality Call for Papers (CFP) applications. Use when the user wants to apply to a tech conference and needs to draft abstracts, outlines, and bios based on their existing work.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Resolves open GitHub Issues in parallel by fanning out independent subagents and then fanning in to aggregate lessons learned.
(🥑) Expert guide for authoring, building, testing, and publishing technical articles to ricc.rocks and Medium.
Hackathon security guide to prevent leaking secrets. Based on Romin Irani's article.
💛 Expert guide for interacting with Riccardo's Obsidian vault (The Carlessian Vault).
Record browser-based video demos from YAML storyboards using shot-scraper.
Installs a lightweight CPU and RAM monitoring cron job and visualization script for agents on the local machine.
| name | devrel-cfp-generator |
| description | A specialized workflow for crafting high-quality Call for Papers (CFP) applications. Use when the user wants to apply to a tech conference and needs to draft abstracts, outlines, and bios based on their existing work. |
| metadata | {"version":"0.0.3"} |
| compatibility | Gemini CLI |
This skill guides you through a multi-phase process to create winning CFP applications. It leverages existing project documentation, past talk history, and conference-specific themes to craft tailored proposals.
Before starting, familiarize yourself with these resources:
references/cfp_checklist.md as your step-by-step guide. Follow the 4 phases strictly.assets/proposal_template.md as the deterministic format for your drafts.assets/riccardo_bio_templates.md for standard Riccardo bios.scripts/validate_proposal.py to check character limits and section compliance.When triggered, immediately copy references/cfp_checklist.md into the local project workspace (e.g., as CFP_CHECKLIST.md) so you can interactively check off items as they are completed. Then begin executing Phase 1: Gathering Constraints.
Do not proceed to Phase 2 until all constraints and Meta info (Demo, Duration) are gathered. Use the validation script in Phase 3 before presenting the final result.