Loading...
Loading...
Found 62 Skills
Use when platform-reported conversions disagree with GA4/ecommerce, when you suspect Meta and Google are double-counting the same sales, or for a standing (monthly) reconciliation workbook that de-dups stacked credit against an order-ID truth set, normalizes attribution windows and currency, compares attribution models, and reads incrementality from a geo/holdout test. Not for the point-in-time R2 veto or RQS gate — use ad-account-auditor; not for the ROI/ROAS ratio math itself — use roi-calculator; not for organic dark-social share attribution or GA4 direct-traffic decomposition — use dark-social-attributor. 付费广告归因对账/去重/增量
Comprehensive GitOps methodology and principles skill for cloud-native operations. Use when (1) Designing GitOps architecture for Kubernetes deployments, (2) Implementing declarative infrastructure with Git as single source of truth, (3) Setting up continuous deployment pipelines with ArgoCD/Flux/Kargo, (4) Establishing branching strategies and repository structures, (5) Troubleshooting drift, sync failures, or reconciliation issues, (6) Evaluating GitOps tooling decisions, (7) Teaching or explaining GitOps concepts and best practices, (8) Deploying ArgoCD on Azure Arc-enabled Kubernetes or AKS with workload identity. Covers the 4 pillars of GitOps (OpenGitOps), patterns, anti-patterns, tooling ecosystem, Azure Arc integration, and operational guidance.
Use this skill when designing chart of accounts, automating reconciliation, managing AP/AR processes, or streamlining month-end close. Triggers on chart of accounts, bank reconciliation, accounts payable, accounts receivable, month-end close, journal entries, accruals, and any task requiring bookkeeping process design or automation.
How to read experiment results without fooling yourself. Confidence intervals, p-values, multiple testing, sequential testing, CUPED, heterogeneous treatment effects, ratio metrics, network effects, dashboard reconciliation, and the interpretation failures that produce confidently wrong shipping decisions.
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
Application-developer GitOps work for OpenChoreo — onboarding Components (BYO image or source-build), authoring Workloads and `workload.yaml` descriptors, attaching PE-authored Traits, wiring component dependencies, generating ComponentReleases and ReleaseBindings via `occ` file-mode, promoting releases across Environments (single, project-wide, bulk), applying per-environment overrides, opening PRs upstream, and verifying Flux reconciliation. Use when the user says 'add a component to the GitOps repo', 'release my service via Git', 'open a PR for this Workload change', 'promote to staging via Git', 'bulk-promote my project', 'roll back a release', or operates a developer-side change from inside a scaffolded GitOps repo.
Guides supply chain management—sourcing and supplier qualification, procurement and PO governance, demand forecasting and inventory policy, logistics and fulfillment (3PL, Incoterms, lead times), supplier scorecards, cost and TCO analysis, supply risk and continuity, and SCM KPI dashboards. Use when designing supply strategy, running RFQs, setting safety stock, resolving stockouts or excess inventory, improving OTIF, dual-sourcing critical parts, or building supplier business reviews—not for contract legal redlines (commercial-counsel), vendor security assessments (information-security-engineer), DC construction delivery programs (senior-data-center-capacity-delivery-manager), compute GL and invoice reconciliation (compute-accounting-manager), SaaS quote-to-order (deal-operations-administrator), or enterprise strategy cases (business-consultant).
Use when a Hermes Kanban worker wants to run Codex CLI as an isolated implementation lane while Hermes keeps ownership of task lifecycle, reconciliation, testing, and handoff.
Use when an approved Spec Kit `plan.md` + `spec.md` must be decomposed into dependency-ordered `tasks.md`, or when `tasks.md` is missing/stale after planning or reconciliation changes.
Design and operate reconciliation processes that ensure data accuracy across portfolio management custodian and clearing systems. Use when building or evaluating a daily position cash or transaction reconciliation process, investigating discrepancies between internal systems and custodian records, diagnosing recurring break patterns especially from corporate actions or pricing differences, setting tolerance thresholds for position cash or market value matching, implementing three-way reconciliation across advisor system custodian and clearing firm, designing break investigation workflows with aging and escalation, normalizing data across multi-custodian feeds from Schwab Fidelity or Pershing, reconciling cost basis tax lots or accrued income across systems, evaluating reconciliation platforms like Arcesium Duco or Advent Geneva, or preparing for regulatory examinations on books and records accuracy.
Regenerate an existing printed CLI from scratch under the current Printing Press, with prior research and prior novel features carried into the novel-features subagent's reprint reconciliation rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".
ARK-style single-stock disruptive-innovation diagnostic. Suitability gate on 4 dimensions (platform fit / innovation revenue / R&D intensity / management vision); if it passes, builds TAM (low/base/high), Wright's-Law cost curve with sourced learning rate, three-scenario 5-year target (Bull/Base/Bear, 15% discount), risks, conditional action frame. Data: Longbridge CLI first, MCP fallback, WebSearch only for TAM / learning rates / industry runway. Runs cross-statement reconciliation BEFORE analysis. Closes with a data-source appendix whose final row is the reconciliation summary. Independent implementation — not affiliated with ARK Invest. Triggers: "木头姐", "ARK", "ARKK", "颠覆式创新", "莱特定律", "TAM", "5年目标价", "情景分析", "AI 与大数据", "自动化与机器人", "能源存储", "基因革命", "区块链与金融科技", "木頭姐", "顛覆式創新", "萊特定律", "5年目標價", "Cathie Wood", "ARK Invest", "disruptive innovation", "Wright's Law", "learning rate", "bull base bear", "scenario analysis".