1,818 skills found · Page 39 of 61
BankrBot / trustlayer-sybil-scannerFeedback forensics for ERC-8004 agents. Detects Sybil rings, fake reviews, rating manipulation, and reputation laundering across 20 chains. No API key needed.
BankrBot / hermesoneInstall, update, and manage the Hermes One desktop app via the `hermesone` npm package
BankrBot / onair-shoutoutSubmit a sponsor message to be read live on air on the GM Farcaster show, via the paid On-Air Shoutout API. Use this when the user wants to buy/book/submit a sponsor read, shoutout, or live ad on GM Farcaster.
BankrBot / aeon-distribute-tokensBatch token payouts via the Bankr Wallet API with per-recipient idempotency, two-phase resolve→execute, dry-run preview, and recovery from partial runs. Re-runs within the same UTC day are a no-op for completed rows.
BankrBot / codegridCodeGrid is a native macOS canvas where multiple coding agents (Claude, Codex, Gemini, Cursor, Grok, shells) run side by side in panes and collaborate via a local agent bus — no tmux, no cloud, no account, no stored API keys.
BankrBot / papertradeTrade Papertrade's synthetic BTC and ETH perps (HyperEVM, priced from Hyperliquid) from a Bankr wallet with REAL USDC, and earn USDC from the PAPER that losing trades mint.
pashov / solidity-auditorSecurity audit of Solidity code while you develop. Trigger on "audit", "check this contract", "review for security", "loop mode", "run the auditor in loop mode", "run 3 passes". Modes - default (full repo) or a specific filename.
Aaronontheweb / api-designDesign stable, compatible public APIs using extend-only design principles. Manage API compatibility, wire compatibility, and versioning for NuGet packages and distributed systems.
Aaronontheweb / type-design-performanceDesign .NET types for performance. Seal classes, use readonly structs, prefer static pure functions, avoid premature enumeration, and choose the right collection types.
Aaronontheweb / snapshot-testingUse Verify for snapshot testing in .NET. Approve API surfaces, HTTP responses, rendered emails, and serialized outputs. Detect unintended changes through human-reviewed baseline files.
Aaronontheweb / verify-email-snapshotsSnapshot test email templates using Verify to catch regressions. Validates rendered HTML output matches approved baseline. Works with MJML templates and any email renderer.
microsoft / powerbi-report-cliPlan, design, author, preview, publish, and manage Power BI reports across requirements, page design, local PBIR/PBIP edits, validation, screenshots, Fabric upload/download, and rebinding.
fy-agent / trellis-channelUse Trellis channel for live multi-agent collaboration, spawned workers, cross-agent review, progress inspection, forum channels, and channel log debugging.
fy-agent / trellis-session-insightReach into past AI conversation history through the `trellis mem` CLI
yuezhiai / openkb-html-criticUse to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stac…
xuzhougeng / singlecell-qcUse when designing, reviewing, or implementing single-cell RNA-seq QC in Python or R with a human-in-the-loop, data-driven approach.
xuzhougeng / word-zotero-citationsBuild, audit, authorize, recover, or finalize dynamic Zotero citations and bibliographies in Microsoft Word DOCX files with a protected-source, digest-bound workflow.
xuzhougeng / figure-composerCompose or improve a publication-grade multi-panel scientific figure from a claim, concrete data paths, or an existing image. Use for figure outlining, parallel panel rendering, exact-grid composition, visual inspection, and adversarial figure review.
xuzhougeng / OpenAlexRetrieve, verify, and synthesize scientific literature. Use for seminal-paper lookups, evidence summaries, method comparisons, and gap analyses. Every citation must come from a live lookup, never from memory; retractions are checked; the deliverable is argued prose with resolvable DOI links.
brycewang-stanford / acl-author-responseUse when drafting an ACL author response inside an ACL Rolling Review cycle on OpenReview, covering the response window before meta-review, reviewer discussion dynamics, score-change strategy, flagging review issues to the area chair, anonymity rules, and deciding between responding now versus revis…
brycewang-stanford / acl-camera-readyUse when preparing an accepted ACL main-conference or Findings paper for camera-ready, covering the extra content page, de-anonymization and acknowledgements, AI-assistance disclosure, keeping the Limitations section, ACL Anthology metadata and CC BY 4.0 publication, meta-review-driven edits, and pr…
brycewang-stanford / acl-review-processUse when reasoning about how an ACL paper travels through ACL Rolling Review and conference commitment, covering reviewer and area-chair roles, meta-reviews, the commitment decision by senior area chairs and program chairs, Findings versus main-conference outcomes, ethics review escalation, and resu…
brycewang-stanford / acl-workflowUse when planning an ACL project calendar across ACL Rolling Review cycles, covering cycle selection against conference commitment windows, backward planning from an ARR deadline, the review-response-meta-review timeline, commitment decisions, resubmission loops to later cycles, and camera-ready thr…
brycewang-stanford / ase-review-processUse when reasoning about how an ASE (IEEE/ACM Automated Software Engineering) research submission is evaluated, covering double-anonymous review, the early-rejection stage before rebuttal, the Accept / Revision / Reject outcomes, the criteria-bound revision round, and how ASE's process differs from…
brycewang-stanford / ase-submissionUse when auditing an ASE (IEEE/ACM Automated Software Engineering) research-track submission for HotCRP readiness, covering the ACM acmart sigconf template and the 10+2 page budget, double-anonymous review, the mandatory Data Availability Statement, the early-rejection stage before rebuttal, and des…
brycewang-stanford / asplos-author-responseUse when drafting an ASPLOS author response inside the short fixed window — triaging reviews into factual errors versus questions versus disagreements, budgeting for the ~800 words reviewers are expected to read, arguing only from evidence already in the submission, and positioning the paper for the…
brycewang-stanford / asplos-related-workUse when positioning an ASPLOS submission against three communities' literatures at once — covering the architecture, OS/systems, and PL/compiler lanes plus accelerator and prior-ASPLOS lines, handling own-work and arXiv material under the 2027 double-blind rules, and meeting the full-name/DOI citat…
brycewang-stanford / asplos-review-processUse when reasoning about how an ASPLOS submission will be judged — the two-page rapid-review screen and what it filters, full double-blind review, the author-response window, the Accept / Major Revision / Reject outcome set, how revisions are re-reviewed as submissions, and where authors actually ho…
brycewang-stanford / asplos-supplementaryUse when deciding what goes into an ASPLOS submission's appendices versus the 11 self-contained pages — applying the rule that reviewers are neither required nor encouraged to read supplemental material, using anonymized supplements for unciteable own work, and staging content for the revision and a…
brycewang-stanford / asplos-writing-styleUse when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include…
