260 skills · sorted by relevance
Reconcile accounting records with payment service payouts, identify discrepancies, possible duplicates, and missing receipts, then prepare a plain-English profit and loss summary with an Excel workbook and a one-page PDF for month-end review.
Look up a project's existing UI components in Storybook, including their props, or configuration inputs, and usage examples. Use the findings to answer questions and identify components to reuse before building duplicates.
Organize open GitHub issues by category, risk, linked pull requests, duplicate candidates, and inactivity. Optionally analyze selected issues in depth, draft responses, and apply approved comments, labels, or closures to keep the backlog actionable.
Organize scattered files by type, purpose, or date, find duplicates, and review older material. Get a proposed folder structure, then approve file moves and renaming, with confirmation required before any deletion.
Explore a table or data file before starting analysis. Summarize its structure, missing values, duplicates, and distributions, flag potential quality issues, and suggest useful measures, grouping columns, and follow-up analyses.
Organize Happy's GitHub issues, find duplicates, and check whether reported bugs are fixed on main, the primary development branch. Prepare replies and proposed actions for maintainer review, with explicit approval required before changes affecting contributors.
Organize scattered files by type, purpose, or date, find duplicates, and review older material. Get a proposed folder structure, then approve file moves and renaming, with confirmation required before any deletion.
Use when designing, reviewing, or troubleshooting Salesforce duplicate prevention, matching rules, duplicate rules, and merge governance. Covers cleaning up duplicates that already exist at ordinary volume: merge sequencing, survivorship, stewardship ownership. Also covers the deployable MatchingRule / DuplicateRule metadata, the Alert-vs-Block action pair, DuplicateRecordSet reporting, and the Apex DMLOptions.DuplicateRuleHeader.allowSave bypass. Triggers: 'duplicate rule', 'matching rule', 'merge strategy', 'dedupe', 'survivorship', 'D&B', 'same contact twice', 'clean up duplicate records', 'clean up duplicate accounts', 'DUPLICATES_DETECTED', 'allowSave', 'FindDuplicates'. NOT for cleanup at volume — hundreds of thousands of records, batch merge jobs, DemandTools/Cloudingo — use data/large-scale-deduplication. NOT for which field values and child records the platform keeps in a merge - use data/record-merge-implications.
The English summary is being prepared. Showing the original description.
Investigate duplicate OpenClaw pull requests and issues using local history and current GitHub evidence. Organize confirmed or suspected duplicates in prtags, recording the decision, confidence, and reasons for maintainers.
Prepare LLM training datasets with NeMo Curator by removing duplicates, filtering low-quality content, and redacting personal information. The skill also covers image, video, and audio curation, including GPU processing and distributed workflows.
Turn git changes since the last tag into clear App Store release notes. Identifies updates users will notice, groups new features, improvements, and fixes, removes internal work and duplicates, and checks each bullet against the actual changes.
Build data quality checks with Great Expectations, dbt tests, and data contracts, which define shared expectations between teams. Check missing values, duplicates, and freshness, then integrate validation into data pipelines and CI/CD.
Prepare spreadsheet data for analysis by finding extra spaces, inconsistent capitalization, numbers stored as text, mixed date formats, and duplicates. Review proposed fixes, apply traceable formula-based changes, and compare results before and after cleanup.
Build a central vulnerability dashboard with DefectDojo to combine scanner findings, remove duplicates, and track remediation. Includes Docker deployment, automated scan imports from CI/CD pipelines, Jira ticket integration, and API queries for reporting metrics.
Build a workflow that extracts and deduplicates threat indicators such as URLs and IP addresses, creates readable reports with links disabled, and prepares standardized STIX 2.1 data for sharing through MISP or TAXII.
Analyze threat intelligence feeds to extract indicators of compromise, observable clues of possible attacks, and their campaign context. Assess source quality, standardize formats, remove duplicates, and enrich indicators for distribution to security monitoring systems.
Collect public posts across a blog, newsletter, or feed archive and save clean Markdown pages for each article. The workflow avoids duplicates, supports resumed runs, repairs empty results, and hands articles to a separate enrichment skill.
Check names, aliases, and existing pages before saving content to a gbrain knowledge store. The skill reads likely matches to identify duplicates, links to existing information, and routes new material to the appropriate ingestion skills.
Investigate Apache ShardingSphere issues using official documentation, code, tests, and issue discussions. Distinguish bugs, unsupported usage, duplicates, and enhancement requests, then draft a concise maintainer-style reply explaining the evidence and next action.
Assess Verdaccio issues against the code, affected release lines, and related reports. Distinguish bugs from configuration problems or duplicates, then propose existing labels, next steps, and a reply draft backed by evidence.
Assess OpenShell issues by checking first-hand use cases, reproduction evidence, existing behavior, and duplicates. Prepare a concise technical assessment, request specific missing information, and leave acceptance and roadmap decisions to human maintainers.
Turn GitHub issue reports into actionable work by searching for duplicates, attempting reproduction, and assessing user impact. Organize issues with existing labels, appropriate owners, and milestones, while clearly recording what was and was not verified.
Turn rough bug reports or requests into Linear issues with clear symptoms, reproduction steps, evidence, and routing details. Check for duplicates, distinguish observations from guesses, and present the proposed issue for approval before creating it.
Review open issues and discussions to organize a project's backlog. Identify possible duplicates, suggest priorities and labels, and record the top five actionable items and cases needing human attention in a state file.