ml-experiment-tracker
Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.
Real OpenClaw skills, parsed from public source files. No mock records, no fabricated metrics.
Showing 193-240 of 256 skills
Page 5 / 6
Plan reproducible ML experiment runs with explicit parameters, metrics, and artifacts. Use before model training to standardize tracking-ready experiment definitions.
Generate reusable multi-step agent workflow blueprints. Use for trigger/action orchestration, deterministic workflow definitions, and automation handoff artifacts.
Scaffold MCP server projects and baseline tool contract checks. Use for defining tool schemas, generating starter server layouts, and validating MCP-ready structure.
Get a disposable temp phone number and receive OTP codes to sign up on websites without using your real number. Handles x402 crypto payment automatically.
Autonomous wallet operations for AI agents on Monad — swap, stake, deploy wallets, trade memecoins, and manage spending policies via natural language.
Integrate Self (self.xyz) — a privacy-first identity protocol using zero-knowledge proofs to verify passports and ID cards. Use when the user mentions Self protocol, Self identity, self.xyz, passport verification, zero-knowledge identity verification, SelfAppBuilder, SelfBackendVerifier, SelfVerificationRoot, or wants to add privacy-preserving KYC, age verification, nationality checks, OFAC screening, or Sybil resistance using real-world identity documents. Covers frontend QR code integration, backend proof verification, and on-chain smart contract verification on Celo.
Send USDC to molty users via A2A protocol. Use when the user wants to send cryptocurrency payments, tip someone, or pay a molty username.
Send USDC to an Ethereum address or ENS name. Use when you or the user want to send money, pay someone, transfer USDC, tip, donate, or send funds to a wallet address or .eth name. Covers phrases like "send $5 to", "pay 0x...", or "transfer to vitalik.eth".
Add money to the wallet. Use when you or the user want to fund, deposit, top up, load, buy USDC, add funds, onramp, or get USDC. Also use when the wallet has insufficient balance for a send or trade operation, or when someone asks "how do I get USDC?"
Sign in to the wallet. Use when you or the user want to log in, sign in, connect, or set up the wallet, or when any wallet operation fails with authentication or "not signed in" errors. This skill is a prerequisite before sending, trading, or funding.
# crypto-watcher
Query real-time and historical financial data across equities and crypto—prices, market moves, metrics, and trends for analysis, alerts, and reporting.
Query real-time and historical financial data across equities and crypto—prices, market moves, metrics, and trends for analysis, alerts, and reporting.
End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
Register your agent onchain with ERC-8004. Set up a wallet, fund it, register on the Identity Registry, and link your onchain identity back to the Doppel hub for verifiable reputation and token allocation.
End-to-end MegaETH development playbook (Feb 2026). Covers wallet operations, token swaps (Kyber Network), eth_sendRawTransactionSync (EIP-7966) for instant receipts, JSON-RPC batching, real-time mini-block subscriptions, storage-aware contract patterns (Solady RedBlackTreeLib), MegaEVM gas model, WebSocket keepalive, bridging from Ethereum, and debugging with mega-evme. Use when building on MegaETH, managing wallets, sending transactions, or deploying contracts.
Boussole produit et technique pour l'application mobile Nudge, un gestionnaire de tâches pensé pour les cerveaux TDAH, TSA et à mémoire sélective. Utilise ce skill dès que l'utilisateur parle de son app de tâches/productivité pour neurodivergents, mentionne Nudge, demande d'ajouter une feature, pose une question de scope ("est-ce que je devrais…"), de stack ("quelle techno pour…"), de design produit, de modèle de données, ou de prochaine étape. À utiliser aussi quand l'utilisateur propose une nouvelle idée pour l'app afin de vérifier qu'elle ne sort pas du scope MVP, ou qu'il demande "qu'est-ce que je fais ensuite ?" / "où en suis-je ?" pour lui rappeler la tâche en cours. Ce skill contient les décisions produit figées, la stack retenue, les 20 templates de tâches, et la roadmap découpée en tâches T01 à T12 avec leurs sous-tâches estimées.
Page-specific guide for /agents/activation — what the two charts (ACQ AI Activation Rate, AI Weekly Active Users) show, what the Start/End/Locked-as-of filters actually do, what the on-page chatbot is scoped to answer, and the underlying API endpoints. Use this skill whenever someone asks about "the activation page", "that chart", "why did the number change when I changed the filter", or is building/modifying anything on /agents/activation. Also load this into the system prompt of the page's in-app chatbot so it can ground answers in the same documentation everyone else reads. For the underlying metric definitions (what "AI activation" means, cohort methodology), defer to `acq-vantage-retention`. For table schemas and query patterns, defer to `acq-vantage-db`.
Use when building a Solana paywall — charging users for agent actions with on-chain memo-match invoice verification. Generates cryptographically-random memos, builds SOL or USDC transfer transactions for client signing, and verifies payments on-chain by scanning the treasury wallet's signature history. Platform-agnostic — works for any Solana SPL mint and any Solana wallet adapter. Pairs with `printr-swap` and `printr-tokenized-agent` for a full agent-revenue + buyback-and-burn loop on Printr POB tokens.
Framework for ACQ Vantage member retention and activation analysis. Use this skill whenever someone asks about churn, retention, activation signals, onboarding effectiveness, billing source performance, community engagement metrics, or member lifecycle. Also trigger when asked to build, update, or explain a retention/activation report or artifact, verify retention math, explain metric definitions, or investigate churn anomalies. This skill defines how Victor and the team reason about retention — always use it before answering any question involving churn rates, activation rates, or cohort analysis, even if the question seems simple.
Use when working with color naming, color theory, color spaces, color definitions, or any task involving color knowledge - palettes, ramps, gradients, conversions, accessibility, perceptual matching, pigment mixing, print-vs-screen color, CSS color syntax, or historical color terminology. Use this skill whenever the user is choosing, comparing, generating, naming, converting, or explaining colors, even if they do not explicitly ask for "color theory."
Analyze stock correlations to find related companies and trading pairs. Use this skill whenever the user asks about correlated stocks, related companies, sector peers, trading pairs, or how two or more stocks move together. Triggers include: "what correlates with NVDA", "find stocks related to AMD", "correlation between AAPL and MSFT", "what moves with", "sector peers", "pair trading", "correlated stocks", "when NVDA drops what else drops", "find me a pair for", "stocks that move together", "beta to", "relative performance", "which stocks follow AMD", "supply chain partners", "correlation matrix", "co-movement", "related tickers", "sympathy plays", "if GOOGL moves what else moves", "semiconductor peers", "compare correlation", "hedging pair", "sector clustering", "realized correlation", "rolling correlation", or any request about finding stocks that move in tandem or inversely. Also triggers when the user mentions well-known pairs like AMD/NVDA, GOOGL/AVGO, LITE/COHR and wants to understand or find similar re
Case study - role misconfiguration bug class applied to a yield aggregator protocol. Use as a template for applying all 10 bug classes to a single target.
Holochain hApp development assistant covering coordinator/integrity zome architecture, Rust HDK/HDI patterns, entry/link types, CRUD, validation, cross-zome calls, Tryorama testing, TypeScript client integration, and Nix dev environments. USE WHEN writing zome code, designing DHT data models, scaffolding a new project, testing hApps, debugging HDK issues, implementing entry types or links, cap grants, access control, cell cloning, deploying or packaging hApps, or working on any Holochain project.
Expert assistant for querying and analyzing on-chain blockchain data using Dune Analytics. Use whenever the user wants to: analyze blockchain/on-chain data, write SQL for Dune, find wallet activity, track DeFi protocol metrics, analyze NFT trades, monitor token transfers, investigate smart contract events, check token prices on-chain, find top holders, measure DEX volume, or explore any crypto/web3 data. Trigger even if the user doesn't mention "Dune" explicitly — if they want blockchain data insights or on-chain analysis, this skill applies. Also trigger when the user provides a contract address and wants data for it. Enforces credit budget rules (500 warn / 700 block) and free-vs-paid key separation.
Primary pipeline step after /shape and before /write-a-prd. Use to verify current docs, versions, repo patterns, and key unknowns before shaping. Invokes /api-design-review when API contract risk is high. Not for underdefined problems or implementation-ready work.
Page-specific guide for /agents/health — what the composite health score is, how the four bands (Dormant / Lukewarm / Engaged / Champion) are defined, what filters do, what the two charts + at-risk table show, and how the on-page chatbot should answer. Use this skill whenever someone asks about "the health page", the composite score, the bands, or wants to build/modify anything on /agents/health. Also loaded into the system prompt of the page's in-app chatbot. For the underlying retention framework (why signals matter), defer to `acq-vantage-retention`. For cohort-over-time AI adoption questions, defer to `activation-dashboard`.
Help with Devolens/Cryptolens feature-gated licensing, feature flags, product editions, feature templates, HasFeature checks, data-object-backed feature hierarchies, AddFeature upgrades, and entitlement review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.
Help with Devolens/Cryptolens backend license key creation, CreateKey API usage, license templates, server-side access-token scope, payment-success license delivery, customer-linked licenses, product IDs, periods, features, maximum machines, and license provisioning workflows.
Help with Devolens/Cryptolens payment automation for Stripe, n8n, Zapier, webhooks, external payment providers, license delivery, renewal, cancellation, CRM sync, expiry reminders, CreateKey, ExtendLicense, BlockKey, AddFeature, and MachineLockLimit workflows.
Help with Devolens/Cryptolens subscription licensing, expiry checks, renewal logic, grace periods, ExtendLicense renewals, BlockKey cancellation handling, Stripe webhook flows, and subscription access review across .NET, Python, Java, Node.js, direct Web API integrations, and related stacks.
Defines architecture principles, catches design problems before code is written, and detects drift as delivery proceeds. Use this skill whenever the user wants to: review a system design or architecture proposal, evaluate trade-offs between technical approaches (microservices vs monolith, sync vs async, edge vs cloud), identify architectural anti-patterns or hidden coupling, enforce service and component boundaries, review integration design or data flow, validate non-functional requirements, detect architecture drift, or self-review a design before presenting it to the team. Also trigger when the user asks "is this the right approach", "what are the trade-offs", or "does this architecture scale".
Activate when classifying data (PII, sensitive, internal, public), running a Privacy Impact Assessment (PIA/DPIA), defining retention or deletion policies, designing GDPR/CCPA compliance workflows, handling subject access requests (SAR) or right-to-erasure, evaluating cross-border data transfers (EU SCCs, adequacy decisions), scoping data minimisation, reviewing new third-party data sharing, or assessing EU AI Act Article 10/13 data transparency obligations for an ML/LLM feature that trains on user data. Use before a feature that collects, stores, shares, or trains on user data is shipped.
Activate when the user wants to create a Product Requirements Document (PRD) from scratch, convert rough ideas or bullet points into a structured PRD, validate or improve an existing PRD, facilitate discovery sessions to extract requirements, review a PRD for completeness before it enters the development workflow, or prepare a PRD that will feed into the SDLC pipeline (requirements-tracer, specification-driven-development, design-doc-generator). Also trigger for: "write a PRD", "define the product", "what are we building", "capture requirements", "product spec", "feature definition", "we have an idea", "turn this into requirements", "requirements document", "product brief".
Governs contract-first and specification-driven development — defining interfaces, schemas, and workflows before implementation begins. Use this skill whenever the user wants to: write an OpenAPI 3.x specification, author a Protobuf or gRPC schema, define an AsyncAPI spec for event-driven interfaces, write a GraphQL schema, write a JSON Schema, review an API contract for completeness or correctness, detect breaking vs non-breaking changes, design a workflow or sequence before coding it, or validate that an implementation matches its contract. Also trigger for: "define the interface before coding", "API spec", "contract-first", "freeze the contract", "service contract", "define the schema", "sequence diagram", "API design", "contract review", "Protobuf", "AsyncAPI", "OpenAPI", "gRPC schema", "GraphQL schema", "schema-first GraphQL", "write the schema before resolvers", "GraphQL API design".
Identifies, rates, owns, and tracks technical and project risks. Use this skill whenever the user wants to: create or update a risk register, identify risks in a new design or delivery plan, rate a risk using probability and impact, design a mitigation strategy, track risk status, or define early warning indicators for specific risks. Also trigger when the user describes risk situations without naming them: "what could go wrong", "I'm worried about the timeline", "this dependency is outside our control", "technical risks", "delivery risk", "risk assessment", "risk mitigation", "risk tracking", "early warning".
Activate when establishing code review processes, writing or improving PR review checklists, setting quality gate policies for CI/CD pipelines, reviewing code quality, setting merge criteria, defining linting and static analysis tool configurations, or coaching engineers on effective review practices. Use for everything from individual PR reviews to systemic quality improvement programmes, including identifying recurring defect patterns and measuring review effectiveness.
Activate when designing or evaluating a testing strategy, defining test pyramid ratios, writing test plans for a release, establishing acceptance test frameworks using BDD/Given-When-Then, setting up contract testing between services, designing performance and load test scenarios, defining test environment strategy, or determining what constitutes "done" for a feature. Also trigger when integration tests are failing and the cause is unclear, or when test execution time is blocking delivery velocity.
Activate when designing or reviewing observability strategies, defining SLOs and error budgets, evaluating monitoring and alerting configurations, reviewing logging and tracing implementations, investigating production incidents through metrics and logs, designing on-call runbooks, assessing whether a service is production-ready from an operational perspective, defining DORA metrics collection, planning reliability engineering work, or evaluating partner company observability implementations against agreed NFRs. Use for everything from setting up the three pillars (metrics, logs, traces) to running error budget reviews and reliability retrospectives.
Activate when investigating performance problems, capacity planning, defining performance NFRs, reviewing load test results, designing auto-scaling strategies, analysing query performance, identifying bottlenecks in distributed systems, troubleshooting latency regressions, evaluating partner company performance test evidence, designing chaos engineering experiments, reviewing reliability patterns (circuit breakers, bulkheads, retries, timeouts), or determining whether a system meets its performance SLOs under realistic production load. Use for any work where response time, throughput, or system resilience under stress needs to be measured, designed, or improved.
Use this skill when building the memory snapshot and iNFT minting feature — exporting project memory to a JSON bundle and minting it as an ERC-7857 iNFT on 0G testnet. Triggers when asked to implement exportSnapshot, mintINFT, or anything touching the iNFT contract or snapshot file format.
Shared cross-language guidance for Cryptolens software licensing SDKs, direct Web API 3 HTTP integrations, and unsupported-language fallbacks. Use when Codex works on any Cryptolens SDK or app integration and needs language-agnostic licensing rules, especially license key verification best practices, offline license verification with cached signed license files or strings, floating licenses, trial licenses, activation semantics, node-locking, machine-binding assumptions, or behavior that should stay consistent across Python, .NET, Java, Node.js, direct HTTP clients, and future SDKs.
Help with Devolens/Cryptolens floating-license workflows, seat reuse timing, overdraft behavior, activation and deactivation expectations, and floating-license machine checks. Use when Codex needs to design, implement, review, or explain floating licenses across .NET, Python, Java, Node.js, and related integrations.
Help with Devolens/Cryptolens software licensing tasks centered on license key verification, activation, signature checks, product ID checks, expiration checks, and machine-binding assumptions. Use when Codex needs to design, implement, review, or explain license key verification across .NET, Python, Java, Node.js, and related integrations.
Help with Devolens/Cryptolens software licensing workflows that require offline license verification, cached signed license files or strings, air-gapped activation, manual activation files, or offline fallback behavior. Use when Codex needs to design, implement, review, or explain offline license verification across .NET, Python, Java, Node.js, and related integrations.
Help with Devolens/Cryptolens trial-license workflows, verified trials, trial key creation, activation expectations, feature-lock caveats, and trial-related machine binding. Use when Codex needs to design, implement, review, or explain trial-license behavior across .NET, Python, Java, Node.js, and related integrations.
GFV email drafting and sending skill. Defines the Executive's voice, formatting expectations, banned words, and Gmail SMTP integration. Use when asked to draft, write, compose, or send any email. NEVER auto-send — always show draft for approval first. Skip when: internal notes, Slack messages, or non-email communication.
5-phase structured planning methodology: Specification, Pseudocode, Architecture, Refinement, Completion. Enhances GFV planning mode with formalized phases and quality gates. Derived from ruflo sparc-methodology. Use when: new feature implementation, complex integrations, architectural changes, unclear requirements. Skip when: simple bug fixes, config changes, well-defined small tasks, routine maintenance.