Results for “proof”

26 skills

Proofly Automation

Automate Proofly operations through Composio's Proofly toolkit via Rube MCP, including tool discovery, connection management, and workflow execution.

Provides PhD-level mathematical analysis for machine learning, including optimization theory, statistical learning theory, and convergence proofs.

theycallmeholla

Genie Proof Prompts

Rewrite any prompt, instruction, task description, or spec into a "genie-proof" version — instructions so explicit, literal, and loophole-free that even a maliciously literal genie (or an LLM, contractor, or junior dev) could not misinterpret them. Use this skill whenever the user asks to genie-proof, tighten, harden, de-ambiguate, or "make bulletproof" a prompt or instruction; whenever they complain that an AI/model/person "didn't do what I meant," "took me too literally," or "found a loophole"; or whenever they hand over a vague prompt and ask to make it precise, explicit, unambiguous, or idiot-proof. Also trigger on phrases like "wish to a genie," "monkey's paw," "lawyer-proof this prompt," or "leave nothing to interpretation."

Security Triage

Triage MarketingClaw security advisories, drafts, and GHSA reports with shipped-tag and trust-model proof.

Mengto Product Proof Saas

Use when creating or redesigning SaaS or AI product landing pages where a real workflow, interface, or deterministic demo is the central proof—pale atmospheric shells, product UI in the hero, prompt-to-output stories, audience tabs, compact feature modules, honest pricing, and FAQ handoffs.

Rank a topic's user-flow branches by proof priority (value × risk × frequency) right after user-flow-map, ordering the branches, gating variation breadth, and promoting or pruning flows so state-model and ux-variations grow the tree in proof order — writes only existing flow-tree ordering fields, no schema change.

More results

Turn a PR, diff, merge request, or patch stack into one evidence-first review brief with severity, missing-proof checks, and route-outs.

Guide for continuous improvement, error proofing, and standardization. Use this skill when the user wants to improve code quality, refactor, or discuss process improvements.

Mine BOTCOIN tokens by solving AI-generated challenges and submitting on-chain proofs on Base.

Integration Testing

`analysis-agent`/`task-agent`/`review-agent`: use for database, broker, cache, HTTP, framework, process, or transaction seam proof; skip local, portfolio, and release-verdict work.

Marketingclaw Debugging

Debug MarketingClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.

Fomo Automation

Automate Fomo marketing operations through Composio's Fomo toolkit via Rube MCP, with dynamic tool discovery and connection management.

Repeat Failure Analysis

`analysis-agent`/`task-agent`/`review-agent`: use when repeated failure needs a new hypothesis or proof path; skip an initial failure with verified cause and a different action.

Verification Before Completion

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when testing, fixing, or extending the MarketingClaw Control UI GUI with Vitest + Playwright end-to-end checks, mocked Gateway WebSocket flows, mocked dashboard runs, screenshots/videos, or agent-verifiable browser proof.

Discover and use DFlow documentation, Agent CLI, Trading API, Metadata API, Proof KYC, prediction markets, and the hosted DFlow docs MCP. Use before implementing DFlow features or when field-level endpoint details are needed.

Computes the SQuAD metric using torchmetrics, given predictions and ground truth. Use when evaluating question-answering outputs with exact match and F1 scores.

Paper Claim Audit

Verifies that every number, comparison, and scope claim in a research paper matches raw result files, using a fresh cross-model reviewer with no prior context to prevent confirmation bias.

Quality Test Gate

Use `analysis-agent` to map acceptance to validation, `task-agent` to add or run bounded tests, and `review-agent` to assess proof coverage. Skip work with no material change or already-fresh complete validation.

claude-dev-suite

BOB (Build on Bitcoin): hybrid Bitcoin/Ethereum L2 using OP Stack + Bitcoin security. Bridges to Bitcoin via threshold signatures + zk-proofs. USE WHEN: building cross-chain Bitcoin/Ethereum apps, evaluating BOB hybrid model.

Investigates bugs, regressions, and crashes by dispatching four parallel read-only sub-agents, then ranks hypotheses and recommends the fastest proof or fix path.

Performing Clickjacking Attack Test

Test web applications for clickjacking vulnerabilities by assessing frame embedding controls and crafting proof-of-concept overlay attacks during authorized security assessments.

24.6k · bundle

Publish and consume blockchain-verified trading signals on Base. Register as a signal provider, publish trades with transaction hash proof, and subscribe to top performers via REST API.

Transaction-verified trading signals on Base. Register agent as signal provider, publish trades with TX hash proof, consume signals from top performers via REST API. All track records verified against blockchain data. No fake performance claims. Triggers on: "publish signal", "post trade signal", "register provider", "subscribe to signals", "copy trade", "bankr signals", "signal feed", "trading leaderboard", "read signals", "get top traders".

Off-page playbook (Lesson 10, outreach). Turns a vetted link-prospect list into them-focused outreach drafts that earn links without spamming. Picks the RIGHT people (those who LINKED to or MENTIONED our topic — never "people who tweeted it"), gives each a real "excuse" (fresh-angle / new-proof / ego-bait), keeps to ≤1 follow-up, and never makes a pushy link ask. Drafts only — every outward send is operator-gated. Outreach is a tool, not a strategy.

theycallmeholla

Sets up and audits the Claude Code harness for a project: CLAUDE.md, .claude/rules, skills, subagents, settings.json permissions, hooks, verification loop. Commands: kickoff (scaffold new setup), check-playbook (score an existing one), scouting-report (last scorecard), adjust (fix bloat/misplaced instructions), drill (turn advisory prose into real hooks/permissions/CI), decline (record an accepted risk), gameplan (work order with acceptance criteria before building), watch-film (check a diff against that order for scope creep/weakened tests/false claims). Use for setting up Claude Code, or on: "Claude ignores my CLAUDE.md", "it's huge and still misses things", "it said done but ran nothing", "it changed files I didn't ask about", "it weakened a test to pass", "rule, skill, or hook?", "is my setup any good". Not for code quality (code-audit), test coverage (test-assessment), one-off prompt wording (genie-proof-prompts), new skill authoring (skill-creator), or compacting a conversation (handoff).