212 skills · sorted by relevance
Use when reasoning about cash runway — burn shape, fundraise triggers, layoff-vs-cut-vs-grow decisions. Triggers on 'how long do we have', 'should we raise', 'cut or grow'.
The English summary is being prepared. Showing the original description.
Use when designing levels, comp bands, equity-vs-cash, geo adjustments, or raise vs promotion vs market correction. Triggers on 'set our comp bands', 'is this raise market'.
The English summary is being prepared. Showing the original description.
Recover a fleet whose machines cannot see each other over the file-sync network: establish ground truth at the hub from the live sync API rather than memory or one peer's claim, publish the hub's verified device id over the messaging rail, and walk each disconnected peer through re-pairing. Triggers: "/raise-sync", "sync is down", "machines cannot see each other".
The English summary is being prepared. Showing the original description.
Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.
The English summary is being prepared. Showing the original description.
Create engineering retrospectives from Git history, covering delivered changes, work patterns, test code ratios, and frequently changed files. Review individual contributions and improvement opportunities, save metrics, and compare results with earlier periods.
Make working code easier to read and maintain while preserving its behavior. The skill identifies tangled conditions, unclear names, duplication, and unnecessary abstractions, then guides small refactoring steps checked against existing tests and project conventions.
Build an HTML fundraising presentation for accelerator partners and angel investors. Organize the opening hook, traction, competitive advantage, and funding request into slides using a dedicated template, with speaker notes and presentation controls.
Review Front-End Checklist rule files and improve their instructions, explanations, and code examples. Use the project's quality scorer and structure validator to identify gaps, replace vague prompts, and organize each rule into a usable reference for developers and agents.
Check academic references against multiple sources to find errors in authors, titles, dates, volume details, pages, and DOIs. Receive a structured report with issue severity, corrected BibTeX content, or instructions for updating matching Zotero records.
Review and improve statistical reporting in manuscript methods, results, and figure captions. It checks sample definitions, repeated measurements, tests, and uncertainty, then provides revised wording and identifies missing information or issues reviewers may raise.
Build three- to five-year financial projections for early-stage startups, linking revenue, expenses, hiring, and cash balances. Compare conservative, base, and optimistic scenarios, estimate how long cash will last, and model fundraising amounts and ownership dilution.
Revise an existing course by correcting slide text, adjusting layouts, repairing quizzes, updating narration, or reordering pages. Edits preserve the course’s established voice and design while focusing on the specific changes requested.
Prepare for salary negotiations by researching market pay, comparing salary, bonuses, equity, and benefits, and defining a justified counteroffer. Create tailored emails and call scripts, with alternative requests and responses when an employer pushes back.
Import text, files, URLs, repositories, and database content into cognee memory. This skill explains input handling, storage organization, extraction options, and cost estimates, while helping diagnose unsupported arguments and document update errors.
Prepare payroll from timesheets, checking hours, pay, and unusual entries for each employee. Produce a run sheet for the owner to review and approve, with supported staging in Gusto and accounting entries after submission.
Find customers’ exact words about a feature, objection, or competitor across meeting transcripts and emails. Organize quotes with speaker details, dates, sources, and context, while showing which accounts lack source coverage.
Investigate slow jobs, stale data, and timeout alerts by timing the specific operation and comparing monitoring thresholds. Produce an evidence-based verdict that distinguishes insufficient time, stalled work, and false alerts before proposing changes.
Review board memos and strategy briefs with available Claude, Codex, and Gemini models. Compare concerns, supporting arguments, and votes, then turn disagreements into questions to resolve before committing to a major business decision.
Collect company facts through a structured 12-question founder interview and save them in a shared context file for AI executive advisors. Capture business, financial, team, and strategic information when setting up advisors or updating company circumstances.
Review spending and fundraising plans through six financial questions covering cash runway, customer economics, ownership dilution, alternatives, margins, and downside survival. Produce a verdict, conditions for funding, and three concrete next steps.
Evaluate a strategic choice through multiple executive roles, each forming an independent view before discussion. Produce a board memo with recommendations, votes, dissent, risks, and success or stop conditions for the founder's decision.
Route business questions to relevant executive advisor roles, coordinate discussions across multiple functions, and combine their findings into clear agreements, disagreements, and action items. Record decisions and flag approved decisions that are due for review.
Capture company context through a structured founder interview covering seven areas, from company identity to goals. Create a shared reference file for C-suite advisor skills and refresh it quarterly or after major business changes.
Switch PUA commentary to an empathetic, encouraging tone while retaining its underlying work and verification requirements. The skill combines specific praise, practical suggestions, and occasional friendly teasing, with variations for different PUA styles.