Results for “reviews”

Reviews and tailors Product Manager resumes against 10 best practices including the XYZ+S formula, keyword optimization, and job-specific customization.

Creates, edits, and analyzes .docx files by unpacking OOXML, using docx-js for new documents, and applying tracked changes for reviews.

Creates, structures, and reviews technical documentation using the Diátaxis framework, organizing content into tutorials, how-to guides, reference material, and explanations.

Conduct systematic literature reviews by searching multiple academic databases, synthesizing findings, and generating professionally formatted documents with verified citations.

Creates a cyber-themed terminal deck for CLI, agent, or dev tool reviews with CRT scanlines, green monospace text, and three-tier tags.

以论文作者身份完成学术审稿 rebuttal 全流程。当用户提供审稿意见（reviewer comments / reviews / meta-review）和论文文件（PDF/LaTeX/DOCX/Markdown），需要分析审稿意见、判断是否需要修改论文、修改论文并撰写给审稿人的逐条回复（rebuttal / response letter / author response）时使用。触发词包括：rebuttal、审稿意见回复、回复审稿人、response to reviewers、审稿人意见、major/minor revision 回复。

Creates safety alert decks with hazard stripes, tiered cards, and policy code blocks for incident reviews and risk communication.

Produces academic papers, literature reviews, grant proposals, and clinical reports with LaTeX formatting and verified citations, using research-lookup and parallel-web skills.

Build board and investor update decks with structured narratives, metrics dashboards, and C-suite perspectives for board meetings, quarterly reviews, and fundraising.

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something

Reviews an academic paper using the NeurIPS review form with three reviewer personas, ensemble scoring, and reflection refinement. Extracts text from PDF, runs structured review, and outputs actionable feedback.

Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something

Comprehensive guide to prevent unmaintainable code, especially from AI generation. Covers code duplication, documentation, error handling, naming conventions, architecture, performance, dependencies, modularity, testing, and technical debt prevention. Essential for code reviews and ensuring long-term code health.

Load this skill when the user says "verify-implementation", "verify implementation", or "/verify-implementation". Reviews the implementation against the issue requirements and project coding standards, runs automated checks, and produces a gated report before acceptance criteria are ticked off.

Transforms source materials (URLs, PDFs, DOCX, Markdown, text, screenshots) into a single-file HTML web article that is visually polished, offline-accessible, and shareable, using a structured editorial workflow with checkpoints and quality reviews.

Facilitate structured post-incident reviews to identify root causes, document what worked and failed, and produce actionable recommendations to improve future incident response.

Write business reports including executive summaries, status updates, postmortems, competitive analyses, data analyses, and quarterly reviews. Use when communicating findings, decisions, or status to stakeholders. Also trigger for 'executive summary', 'status report', 'postmortem', 'incident report', 'competitive analysis', 'quarterly review', 'business report', or 'data analysis report'.

Reviews pull requests and local diffs against Google's eng-practices code review guide (design, complexity, tests, naming, comments, style, consistency, documentation, every-line, context) and emits a ranked, principle-tagged finding list with rich local diff rendering. Optional follow-up step posts selected findings as a GitHub PR review. Invoke when the user says "googly-eyes this PR", "review by the canon", "principled code review", "Google-style review", "review this CL", or pastes a PR URL and asks for a code review. 👀

>- Run automatic SPICE simulations on subcircuits detected from KiCad schematic analysis — validates filter frequencies, divider ratios, opamp gains, LC resonance, and crystal load capacitance. Supports ngspice, LTspice, and Xyce (auto-detected). Generates testbenches, runs batch mode, produces structured pass/warn/fail report. Use when the user asks to simulate, verify, or validate any analog subcircuit — RC filters, LC filters, voltage dividers, opamp circuits, crystal oscillators. Also for "simulate my circuit", "run spice", "verify with simulation", "check my filter cutoff", "does this divider give the right voltage", "what's the bandwidth of this opamp stage". Consider suggesting simulation during design reviews when the schematic analyzer reports simulatable subcircuits and a SPICE simulator is available.

Complete meeting lifecycle skill — preparation before and follow-up after any professional or personal meeting. Use this skill whenever the user mentions an upcoming meeting, wants to prepare for a meeting, needs an agenda, wants to brief themselves before talking to someone, needs to write up meeting notes, wants to send a follow-up email after a meeting, needs to capture action items, or says anything like "I have a meeting with...", "I just got out of a meeting", "help me prepare for...", "I need to follow up on...", or "what should I ask in this meeting." Also trigger for specific meeting types: job interviews, performance reviews, 1:1s, sales or client calls, and difficult conversations. Both modes are covered: PRE-meeting preparation and POST-meeting follow-up. Trigger proactively even when the user doesn't use the word "meeting" — if they describe a situation where they're about to talk to someone important, or just finished such a conversation and need to capture it, this skill applies.