區塊鏈
Web3、智能合約和加密貨幣技能
2258 skills in this category
Subcategories
discover-cryptography
Automatically discover cryptography skills when working with encryption, TLS, certificates, PKI, and security
OC Authentication Helper
Helper skill to retrieve OAuth tokens from the correct OpenShift cluster context when multiple clusters are configured
Prow Job Analyze Test Failure
Analyze a failed test by inspecting the code in the current project and artifacts in Prow CI job. Provide a detailed analysis of the test failure in a pre-defined format.
validation-rulebook
Use to define validation, freshness, and compliance checks for enriched data.
data-contract-framework
Operating model for defining, enforcing, and auditing BI data contracts.
account-tiering
Use when defining ABM tiers, scoring logic, and coverage rules.
performance-metrics
Use to define KPIs, alert thresholds, and reporting cadences for social calendars.
routing-logic
Use when defining or adjusting marketing-to-sales assignment rules.
metric-governance-kit
Framework for defining, approving, and auditing GTM metrics and KPIs.
mcaf-feature-spec
Create or update a feature spec under `docs/Features/` using `docs/templates/Feature-Template.md`: business rules, user flows, system behaviour, Mermaid diagram(s), verification plan, and Definition of Done. Use before implementing a non-trivial feature or when behaviour changes; keep the spec executable (test flows + traceability to tests).
personalization-logic
Use when defining dynamic content rules, tokens, and conditional offers inside nurture programs.
guardrail-scorecard
Framework for defining, monitoring, and enforcing guardrail metrics across experiments.
pql-framework
Methodology for defining product-qualified lead (PQL) signals, scoring, and routing.
lifecycle-cadence
Use when defining nurture pacing, triggers, and suppression logic.
attribution
Use to define measurement, data sharing, and ROI reporting for joint campaigns.
signal-taxonomy
Use to define schemas, topic tags, and lineage metadata for enriched signals.
crm-hygiene
Use to enforce stage definitions, next-step requirements, and data completeness across the pipeline.
escalation
Use to define incident tiers, response protocols, and stakeholder communications.
suppression-logic
Use to define guardrails that pause signal-driven plays when accounts are risky, saturated, or in-flight elsewhere.
instrumentation
Use when defining events, fields, and governance for GTM analytics pipelines.