644 skills · sorted by relevance
Analyze incoming Slack messages, emails, or escalations before replying. Separate the explicit request from the outcome behind it, clarify requirements and success criteria, and develop a reply or counterproposal while clearly labeling assumptions.
Draft structured RFCs, proposals for gathering feedback before a major decision. Organize background, weighted criteria, alternatives, costs, and a recommendation so stakeholders can compare choices and understand the reasons for the proposed direction.
Create a technical design document before implementation by answering questions about the problem, scope, architecture, risks, and delivery plan. The skill adjusts sections to project size and covers security, testing, monitoring, and recovery where relevant.
Compare three or four ways to frame a talk, with strengths, weaknesses, and audience fit. Generate titles, conference proposal descriptions, and a peer feedback draft, then confirm the chosen direction before scripting.
Learn the complete OpenSpec workflow through a small task in an actual codebase. The agent explains each stage while creating a proposal, specifications, design, and tasks, then implements the change and archives its records.
公司金融实证研究的"漏斗式选题查找器"。互动开场先后询问 (1) 研究方向、(2) 候选标题数量 N， 再扫描全球文献（已出版英文学术期刊 + SSRN working paper + 全球高校 department seminar 1 年内日程），基于 Edmans (2024) "1000 Rejections" 红线生成 N 个候选标题，**通过并行 subagent（Agent 工具）批量生成计划书 + 查新；每个 subagent 必须强制调用 Skill 工具加载 econfin-proposal 与 novelty-check 两个预设 skill 完成各自模块**，**只有当 novelty score >= 9 时（即 JF/JFE/RFS 顶刊层次），subagent 才把 proposal + 查新报告合并的 md 写入 F:\Dropbox\CC\选题大全\<研究方向短名>\（以"简短选题名称-分数"命名，子文件夹名由 Step 0 从用户输入的研究方向派生）；< 9 分的选题在 subagent 内部直接丢弃，绝不写盘、绝不输出**。当用户说"找选题"、"帮我找选题"、"想做 X 方向"、 "empirical CF idea search"、"批量生成研究计划书"、"100 ideas"、"econfin-idea-finder" 时触发。
The English summary is being prepared. Showing the original description.
Evaluate scientific manuscripts and grant proposals for sound methods, statistics, reproducibility, ethics, and clear reporting. Produce a structured review that separates major concerns from minor issues and gives authors specific, constructive suggestions for revision.
How to work in a Software Lifecycle project (the `software-lifecycle` starter pack): proposals → decisions → specs → postmortems, plus guides. Read when the project has these folders, or when asked how this project is organized. Carries the doc lifecycle, status flows, and per-folder agent behaviors so that guidance does not live inside template bodies or folder descriptions. The five workflows — frame a proposal, write a spec, record a decision, write a postmortem, review a design — each ship as their own sibling skill in this pack. Complements the platform `open-knowledge` skill; does not replace it.
The English summary is being prepared. Showing the original description.
Write a blameless incident postmortem under postmortems/ following the Google SRE shape — evidence-based timeline, trigger vs root cause vs symptom, contributing factors, what went well, and owned+dated+verifiable action items. Read when asked to write a postmortem, do an incident review, run a root cause analysis, write up the outage, retro on the outage, or when the user says we had an incident and wants it documented. Do NOT read to frame a proposal (use frame-a-proposal), write a spec (use write-a-spec), record a decision (use record-a-decision), or review a design (use review-a-design) — a postmortem documents an incident that already happened, it does not propose, specify, decide, or critique future work.
The English summary is being prepared. Showing the original description.
Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both directions, plus the supersedes chain that keeps a decision log honest. Read when asked to record an architecture decision, write an ADR, log the decision we made, document why we chose X over Y, capture this decision for the record, or supersede an old decision with a new one. Do NOT read to frame a proposal or explore an idea not yet decided (frame-a-proposal), to write a spec or implementation plan (write-a-spec), to write an incident postmortem (write-a-postmortem), or to judge whether a design is sound (review-a-design). This skill records a decision already made; it does not make one.
The English summary is being prepared. Showing the original description.
Draft a tailored freelance proposal or platform profile bio from a real job posting/brief and the freelancer's actual background. Use when responding to a listing on Contra/Upwork/etc, or writing/updating a freelance profile. Never invents experience, clients, or credentials that weren't provided.
The English summary is being prepared. Showing the original description.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
The English summary is being prepared. Showing the original description.
Generates structured biomedical outlines for review articles, discussion sections, and thesis proposals. Use when a user provides biomedical keywords, results/discussion text, or a proposal title plus background and needs a directly usable academic writing scaffold.
The English summary is being prepared. Showing the original description.
Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template
The English summary is being prepared. Showing the original description.
Build traceable internal-review proposal, RFI, RFP, tender, bid, and questionnaire responses from supplied questions and approved sources. Use to analyze questions, contribute business or product evidence, or draft qualified responses.
The English summary is being prepared. Showing the original description.
Write a conference talk proposal / CFP submission for a tech or developer conference. Use when asked to submit to a CFP, propose a talk, or write a session abstract. Produces a compelling title, abstract, audience takeaways, an outline, and the speaker pitch — tuned to what selection committees actually look for.
The English summary is being prepared. Showing the original description.
Use when asked 帮我写开题报告, 开题答辩怎么准备, 文献综述怎么写, 技术路线图, 研究内容和创新点, or write a thesis proposal for a Chinese university. Produces a 开题报告 in the section order Chinese universities use (选题背景与意义, 国内外研究现状, 研究内容与目标, 研究方法与技术路线, 创新点, 研究基础, 进度安排, 预期成果, 参考文献), a literature review plan, a technical route diagram in text, and the questions the 开题答辩 panel is likely to ask.
The English summary is being prepared. Showing the original description.
Record a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
The English summary is being prepared. Showing the original description.
Record a decision, document existing code, or file a supplied research material, in free text; no first word is a mode. Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, a repeated agent procedure, a user flow with examples over an existing spec, or a finished report or one external material already in hand. Name any document type inside the subject — journey, prd, idea, or cpat included — to get exactly that type. Planning a feature, an investigation not yet done, or an intended user journey the request asks to plan ('plan the onboarding journey') → /archcore:plan. Checking docs against code or docs health → /archcore:review.
The English summary is being prepared. Showing the original description.
Create slides for management meetings and proposals using design rules and 62 layout patterns. Build HTML and PDF decks, check content and layout, and produce editable PPTX files when requested, including pages matching an existing presentation.
Use when judging whether a management/organization literature is an Academy of Management Annals (Annals)-scale review topic — mature, important, fragmented, and integrable into a new framework — rather than a narrow review. Decides fit and frames the review's animating problem; it does not gather the literature (amann-literature-synthesis) or write the proposal (amann-proposal-framing).
The English summary is being prepared. Showing the original description.
Use when running the final pre-submission preflight for an Academy of Management Annals (Annals) proposal or invited full review via the Manuscript Central portal — proposal-vs-invited-review route, deadlines, formatting, CV, and anonymity. Final checks; it does not draft content.
The English summary is being prepared. Showing the original description.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
The English summary is being prepared. Showing the original description.
Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. "respond to this RFP"
The English summary is being prepared. Showing the original description.