Results for “categorize”

Runs small and midsize business bookkeeping operations - categorizes bank and card transactions to a chart of accounts, reconciles a bank or card statement against the ledger, works a month-end close checklist, and produces a close package for the accountant. Works from QuickBooks Online, Xero, bank CSV/OFX, or Mercury exports, and from the Xero, QuickBooks, or Mercury connectors when present. Use it whenever the user says "reconcile", "bank rec", "categorize transactions", "month end close", "close the books", "books don't match the bank", "reconciliation is off by", "uncategorized expenses", or shares a QuickBooks or Xero export or a bank statement CSV, even if they do not name the task. Never plugs a difference; every unreconciled dollar is explained or listed.

The English summary is being prepared. Showing the original description.

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.

• Sorting a growing backlog of open issues
• Checking whether suspected duplicate issues are truly duplicates
• Prioritizing security risks and breaking changes

Generate a read-only security report on threats involving MCP connections and operations. It groups findings by threat, reports the highest severity, and supports table or JSON output with a configurable severity threshold for failure.

• Prepare security findings before a release
• Share a categorized threat report with a security team
• Check changes in MCP-related threats during periodic audits

Create Gmail filters that automatically label, star, or categorize incoming messages. Check existing labels, create a label when needed, define a filter, and verify its settings to organize recurring email.

• Automatically label incoming receipts
• Keep mail from a specified sender out of the inbox
• Check existing labels and configured filters

Turns changelog-scan results into a readable, categorized release notes draft. Places breaking changes and security items at the top and ends with a human review note, providing a proposal for review.

• Turning scan results into a release notes draft
• Organizing release updates by category
• Highlighting breaking changes and security items

Turn scan data into a categorized release notes draft covering features, fixes, breaking changes, and security. Get clean Markdown suitable for a CHANGELOG or GitHub release, with a review disclaimer and human approval required before publication.

• Draft release notes from scan results
• Organize features, fixes, breaking changes, and security updates
• Prepare Markdown for a CHANGELOG or GitHub release

Turn a structured change list into a categorized release notes draft for users. Follow the project's writing style, highlight breaking changes and security items, and include upgrade guidance where evident, leaving publication to human review.

• Drafting release notes from a structured change list
• Organizing features and bug fixes for users
• Highlighting breaking changes and security updates

Turn a talk summary and optional timeline into a numbered, categorized catalogue of ideas. Rate each idea's presentation potential and receive suggestions for grouping strong concepts into a talk structure before choosing an angle.

• Listing ideas before choosing a talk angle
• Comparing concepts for demonstrations and concrete evidence
• Grouping related ideas into a talk structure

Turns Git commits and pull request details into release notes for CHANGELOG.md, a release pull request, and Slack. It categorizes changes, explains user impact in plain language, and flags database migrations that need attention.

• Preparing release notes since the last release
• Summarizing changes across a specified version range
• Drafting a release pull request body

Find and select Squad operations through a categorized menu, from managing an AI team and GitHub issues to choosing models and reviewing activity. The skill collects required options and routes requests to CLI commands or the coordinator agent.

• Find the Squad command for a task
• Add team members or change their roles
• Organize and monitor GitHub issues

Find and start common Squad operations through a categorized menu. The coordinator guides users through team management, GitHub issues, plugins, model settings, and session history, collecting required details and confirming changes where the catalog requires it.

• Find available Squad operations
• Add team members or change roles
• Set models for the team or individual agents

Triggered by "tidy up", "clean up transactions", "categorize uncategorized", "organize my transactions"

The English summary is being prepared. Showing the original description.

Organize, categorize, and summarize business expenses for reimbursement and tax preparation. Use when a user asks to create an expense report, organize receipts, categorize expenses, summarize spending, prepare expenses for reimbursement, or compile business expenses for tax filing. Handles receipts, CSV data, and manual entries.

The English summary is being prepared. Showing the original description.

GitHub 解封 — 账号封禁/限制/恢复的领域操作系统。覆盖：(a) GitHub 官方政策体系 (TOS / 可接受使用政策 / Trust & Safety 执行模式 / 公开申诉路径 / 受制裁地区解读)；(b) 封号原因诊断学 (spam / abuse / 制裁误标 / 2FA 丢失 / ToS 违规 / 账号劫持误判 / ban evasion 等子类型 + 症状→原因映射 + 自我分诊压测)；(c) 申诉实操 craft (写一封能让 T&S 快速判误伤的英文申诉信 + 升级阶梯 + 法务介入边界 + Don'ts)；(d) 制裁与合规硬边界 (OFAC SDN 名单 / 哪些国家或地区真不可达 / VPN 误判路径 / 中国大陆不是美国制裁地区的反复重申)；(e) 中国大陆开发者特别处境 (sanctioned region 误标 + SMS 验证不支持 +86/+852 + Gitee/GitLab/Codeberg/JihuLab 备用迁移 + 私有自托管 Gitea/Forgejo)；(f) 真实案例库 (~30+ 公开案例分类拆解：误伤 / 真违规 / 制裁误标三类各自赔率与申诉成功路径)。伦理锚绝不软化：不教 ban evasion / 不教撒谎式申诉 / 真违规承认改进 / 丢 2FA 无恢复因子则诚实告知 / 中国制裁误标靠申诉不靠换 VPN / 申诉 6 个月窗口必算清 / 约 3% (业内估) 真违规恢复 vs 约 79% (业内估) 误伤申诉成功率分层标。 (GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: false-positive / genuine violation / sanctions mis-flag, each with win-rate and appeal success path). Ethical anchors absolutely not softened: do NOT teach ban evasion (creating new accounts turns a temp ban into a permanent one — the single biggest mistake); do NOT teach social engineering or lying in appeals (misuse + actually confirms violation); genuine violations: admit + improve beats denial; lost 2FA + no recovery factor → do not pretend recovery is possible; China sanctioned-region mis-flag → fix via appeal, not repeated VPN switching; appeal form 6-month window must be counted carefully; historical 约 3% (业内估) genuine-violation recovery vs 约 79% (业内估) false-positive appeal success rate stratification must be honestly labeled. Anti-samples (explicitly describe harm, never endorse): developer permabanned for ban evasion / open-source team org-banned for personal attacks in public issues / cases where repeated VPN switching escalated risk-control severity.) Master OS — automated mastery of GitHub Account Reinstatement — the domain operating system for GitHub (and analogous platform) account suspension, restriction, appeal, and recovery. Covers: (a) GitHub official policy architecture (TOS / Acceptable Use Policies / Trust & Safety enforcement patterns / public appeals pathways / sanctioned-region interpretation); (b) suspension-cause diagnostics (spam / abuse / sanctions mis-flag / 2FA loss / ToS violation / account hijack false-positive / ban evasion taxonomy + symptom→cause mapping + self-triage pressure test); (c) appeal craft (writing an English appeal letter that gets T&S to fast-track a false-positive ruling + escalation ladder + legal-engagement boundary + Don'ts); (d) sanctions and compliance hard boundaries (OFAC SDN list / which countries/regions are truly unreachable / VPN false-positive paths / China is NOT a US-sanctioned region — repeated emphasis); (e) mainland China developer special circumstances (sanctioned-region mis-flag + SMS verification does not support +86/+852 + Gitee/GitLab/Codeberg/JihuLab fallback migration + self-hosted Gitea/Forgejo); (f) real-case library (~30+ public cases with categorized analysis: fa

The English summary is being prepared. Showing the original description.

Build AI expense categorization. TRIGGERS - Use when user needs help with ai-expense-categorizer related tasks.

The English summary is being prepared. Showing the original description.

Synthesize sprint retrospective notes into categorized action items and patterns. Use this skill when: - You have sprint retro notes (raw text, meeting transcript, or structured notes) to process - You need to identify recurring patterns across multiple retros - You want categorized action items with owners and deadlines from retro discussions For a marketing campaign or launch retro that writes learnings to knowledge/, see retro.

The English summary is being prepared. Showing the original description.

Scan the current codebase to identify and categorize every public-facing page (landing pages, product/feature pages, solutions, pricing, resources, blogs, case studies, about, legal) and produce a single authoritative inventory document. Use this skill whenever the user asks to "init overgrow", "set up overgrow", "scan the site", "inventory the pages", "categorize pages", "map the site", or whenever any other overgrow skill needs a baseline page map and none exists yet. Output is a structured markdown inventory at `.overgrow/inventory.md` that all other overgrow skills read from.

The English summary is being prepared. Showing the original description.

Build AI expense categorization. TRIGGERS - Use when user needs help with ai-expense-categorizer related tasks.

The English summary is being prepared. Showing the original description.

Summarize the past 24 hours of Gmail activity into items needing action, items worth attention, and informational updates. Orbit presents the daily digest as an opened email in a Gmail-style reading view using an authenticated Gmail connection.

• Reviewing the past 24 hours of Gmail activity
• Checking messages that need action
• Separating noteworthy updates from informational mail

Check text, code, and configuration files for personal information and secrets before committing, logging, storing, or sending them. Identify categorized findings, flag their locations, and suggest redaction to hide sensitive details.

• Check code for personal information before committing
• Inspect logs before saving them
• Check model responses before sending them

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Review code for security, performance, quality, and ease of maintenance. Receive an overall assessment and categorized findings, with file locations, severity, impact, and code examples for addressing critical issues.

• Reviewing a pull request
• Checking authentication and sensitive data handling
• Finding inefficient algorithms or database queries

Review code for security, performance, quality, and ease of maintenance. Receive an overall assessment and categorized findings, with file locations, severity, impact, and code examples for addressing critical issues.

• Reviewing a pull request
• Checking authentication and sensitive data handling
• Finding inefficient algorithms or database queries

Collect indicators of compromise, technical clues such as suspicious domains and file hashes, from incident evidence. Add context and confidence scores, then prepare them for detection, blocking, and structured sharing with partners.

• Extracting threat indicators from incident evidence
• Adding threat context and confidence scores to indicators
• Preparing indicator lists for detection and blocking