Loading...
Loading...
Found 6,673 Skills
Emergency Triage and Symptom Screening Assistant. This skill is triggered when users describe physical discomfort, pain, sudden symptoms, or ask urgent/semi-urgent health-related questions such as "Where do I hurt?", "I feel unwell", "Which department should I register for?", "Do I need to go to the hospital?", or "Help me judge". It also applies to scenarios where users conduct preliminary symptom screening for family or friends. Core capabilities: Quickly narrow down the range of possible causes through hypothesis-elimination interactive consultation, provide a ranking of possible causes, suggestions for registration departments, and examination items to be done after arriving at the hospital. Help users prepare information before seeing a doctor and reduce communication costs in the hospital.
Hedging strategy design framework — Beta hedge ratio (portfolio vs benchmark), option protection strategies (protective put / collar), tail-risk hedges (VIX-related / gold / treasuries), cross-asset hedges (currency risk), and hedge cost assessment (option premium vs protection value). Triggers: "对冲", "对冲策略", "Beta对冲", "保护性看跌", "领口策略", "尾部风险", "汇率对冲", "对冲比率", "對冲", "對冲策略", "Beta對冲", "保護性看跌", "領口策略", "尾部風險", "hedging", "hedge strategy", "beta hedge", "protective put", "collar strategy", "tail risk hedge", "currency hedge", "hedge ratio", "portfolio insurance".
Patterns and conventions for creating a good PR
Write production-ready print stylesheets. Covers @page rules, page breaks, visibility, color management, typography, images, links, tables, and framework-specific gotchas for Next.js/React/Tailwind. Use when the user asks to add print styles, make a page printable, or create a print-friendly layout.
Cloud object storage integration with AWS S3, Azure Blob Storage, and Google Cloud Storage. Covers presigned URLs, multipart uploads, bucket policies, lifecycle rules, and CDN integration. USE WHEN: user mentions "S3", "blob storage", "cloud storage", "object storage", "presigned URL", "file upload to cloud", "GCS", "Azure Blob", "bucket" DO NOT USE FOR: local file uploads - use `file-upload`; database BLOB columns; local filesystem operations
Ship a change via a feature branch and pull request — never directly to the default branch. Use after any code change, fix, refactor, or docs update that needs to land on main. Branches are named `<card-number>` from the FluentBoards card. Commits go through the husky pre-commit hook (lint-staged); pushes go to the feature branch only; the PR body links back to the card. Hard refuses any push to main / master / trunk.
Add a single functional spec to the ***functional specs*** section of a ***plain spec file. Use whenever exactly one new functional spec is being added — whether the user explicitly asks, or another skill/workflow (e.g. forge-plain, add-feature) needs to author a new functional spec. Every new entry under ***functional specs*** must go through either this skill or `add-functional-specs` (the bulk variant for adding multiple specs in one pass); hand-authoring functional specs without invoking one of these skills is forbidden.
End-to-end conference talk pipeline: paper → slide outline → Beamer + PPTX → per-page polish → assurance checks (claim / citation / anonymity) → final export and report. Default-good for academic conference talks (NeurIPS / ICML / ICLR / VALSE / 投稿 talks). Trigger phrases: "做 talk", "做 PPT 全流程", "talk pipeline", "end-to-end slides", "做演讲", "conference talk full workflow". Use when the user wants the complete talk artifact, not just a slide deck.
A curated collection of 136+ specialized Codex subagents for development tasks across 10 categories
Walks an SMB owner through month-end close: reconciles QuickBooks against PayPal (and Square/Stripe) settlements, flags uncategorized transactions, suspicious duplicates, and missing receipts, then writes a plain-English P&L narrative and exports a close packet (xlsx + one-page PDF). Use when the user says "close the month," "month-end," "reconcile," "what's missing," "P&L," or asks why revenue or margin changed this month.
Prepare for and respond to SEC and FINRA regulatory examinations across the full exam lifecycle. Use when the user asks about exam notification letters, document request lists, deficiency letter responses, mock examination programs, annual compliance reviews under Rule 206(4)-7, or SEC/FINRA examination priorities. Also trigger when users mention 'we just got an exam letter', 'preparing for our first SEC exam', 'how to respond to a deficiency finding', 'staff interview preparation', 'what does OCIE look for', 'examination readiness checklist', 'sweep exam on off-channel comms', or ask what to expect during a regulatory audit.
Guides people operations (HR ops)—employee lifecycle administration, HRIS workflows, onboarding and offboarding checklists, handbook and policy rollout, benefits and payroll coordination, performance review cycles, leave and PTO process, and people data hygiene. Use when running new-hire onboarding, offboarding, HR policy communications, performance cycle logistics, org change updates in HRIS, or employee-facing process design—not for corporate board governance (corporate-counsel), commercial contract redlines (commercial-counsel), SOC audit evidence (compliance-engineer), or customer success onboarding (customer-ops-specialist). Escalate employment law questions to qualified counsel.