3.3K skills · sorted by relevance
Reconcile general ledger and subledger extracts for the same entity, asset class, and date. Match transactions or positions, report differences in amounts, quantities, or posting dates, and summarize likely causes alongside the matching rate.
Investigate incorrect, missing, or unexpectedly changed OpenViking memories by tracing memory files back to archived change records and, when needed, source messages. Return an evidence trail, identify gaps, and suggest next steps without modifying data.
Clarify how a product differs from competitors and test whether buyers value that difference. The skill guides competitor messaging reviews, assessments of hard-to-copy strengths, wording comparisons, and a phased rollout of validated positioning.
Analyze Git changes, group related files for staging, and create commits using Conventional Commits, a structured message format. Infer the change type and scope from the diff, with optional user overrides for the type, scope, and description.
Analyze current Git changes to choose a branch for a feature, release, or urgent fix. Create a descriptive name and switch to the new branch using Git Flow, a structured approach to managing development branches.
Resolve a design question by building a temporary, runnable prototype. Explore logic through clickable scenarios or compare three structurally different interface variants, then record the user's decision while keeping the prototype separate from production code.
Create a competitive brief comparing products or specific features, including pricing, positioning, customer feedback, and market changes. Translate findings into product priorities, differentiation choices, and practical material for sales teams or executive discussions.
Analyze data distributions, trends, unusual values, and differences between groups using suitable statistical methods. The skill guides interpretation of effect sizes, meaning the magnitude of differences, alongside uncertainty and business impact, while checking for misleading conclusions.
Have a different AI model review code, analysis, or documents against the original skill's stated requirements. Receive evidence-based findings and a comparison of agreement and disagreement, then decide which recommendations to accept.
Challenge business plans, prepare for difficult board questions, and work through decisions with painful tradeoffs. This skill identifies assumptions and failure risks, examines stakeholder impacts, and turns postmortems into changes with clear owners and verification dates.
Research five direct competitors and compare their features, pricing, strengths, and weaknesses. Use the findings to understand market positions, identify unmet customer needs, and recommend ways to differentiate a product.
Review code changes for newly introduced security issues with a plausible attack path. Produce findings for the Warden security summary, including affected lines, severity, a minimal fix, and observable conditions for confirming the issue is resolved.
Reconcile Stripe activity and bank transactions against invoice records using consistent fee and timing allowances. Record explained differences in the reconciliation sheet and flag unresolved transactions with supporting references for a person to review.
Review a GitHub pull request or branch and receive a concise summary of its purpose, design choices, and notable code. Check linked issue acceptance and highlight evidence-based concerns through their observable impact on users.
Build distinct, working versions of one interface component and compare them at full size using a visual picker. Explore differences in layout, interaction, or motion, then integrate the version you choose into the project.
Review an existing bug-fix pull request using validated reproduction tests and the complete code diff. Assess root-cause coverage, scope, and regressions, then document behavioral evidence and follow the workflow's branch and approval rules.
Run a quick first review of code changes with six specialist agents working in parallel. They check logic, input and output, shared state, resources, missing behavior, and API completeness, then combine duplicate findings into a report ranked by confidence.
Compare a regulatory change with an indexed company policy library. Identify affected policies, missing or conflicting provisions, responsible owners, and specific changes needed, with source labels and flags for uncertainty about whether the rule is in force.
Prepare English pull requests for Apache SeaTunnel from a change summary, branch history, and file differences. It builds titles and bodies that follow project conventions, records actual testing, and can submit the pull request when requested.
Review an agent's saved context and unread coordination messages at the start of a task. Summarize relevant assignments, move handled messages aside, and prompt the agent to preserve lasting decisions and outcomes before finishing.
Compare a file’s current content with its intended replacement before writing. Skip matching files to avoid unnecessary rebuilds and timestamp changes, with guidance on readable diffs, line endings, encoding, and exact content requirements.
Reviews code changes for security risks using Git history, caller counts, and test coverage. Produces a Markdown report with evidence, potential attack scenarios, affected code, and clear limits on what was reviewed.
Create an interactive HTML guide to a branch’s code changes, with complete file diffs arranged in a logical reading order, explanations of design choices, and review findings labeled by severity.
Work through up to five adaptive questions to clarify your product’s customers, unmet needs, category, benefits, and competitive differences. Turn the answers and supporting evidence into a positioning statement and a concise summary for stakeholder review.