Menu
Skills in this repository
SkillsMP has collected 55 skills from ryanportfolio/AI-Firmware. Open a skill to review its source and details.
ryanportfolio/AI-FirmwareShowing 15 of 55 collected skills.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when drafting or revising prose for a reader: application answers, emails, essays, bios, cover letters, proposals, memos, reports, product copy, speeches, or when a draft reads as machine-made or must match a writer's own voice.
Use when drafting or revising prose for a reader: application answers, emails, essays, bios, cover letters, proposals, memos, reports, product copy, speeches, or when a draft reads as machine-made or must match a writer's own voice.
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy.
Push current branch changes to GitHub and provide a PR comparison link. Use when the user says $pr, asks to create a PR, or wants to push their changes.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when you have a spec or requirements for a multi-step task, before touching code