Explore skills
Showing 32761–32790 of 77079 skills
Audit recent high-relevance papers from a target venue to identify claim-relevant experimental evidence gaps after core P0 results exist. Use for venue completeness and reviewer-risk analysis; not for redefining the research question or running experiments.
cpt13-g/build-research-evidence
Stars: 54Claude CodeCodexUse when reverse-engineering or detecting malware — static triage + capa/YARA-X, emulation/DBI/.NET unpacking, dynamic/fileless/Volatility 3 memory analysis, C2 config extraction (Cobalt Strike/CAPE), C2 traffic detection (JA4+, beaconing)
hypnguyen1209/offensive-claude
Stars: 421Claude CodeCodexUse when pentesting an Android/iOS app — Frida 17 instrumentation, SSL-pinning & root/jailbreak bypass, Android 14/15 CA injection, exported-component/content-provider abuse, deep-link/WebView chains, biometric bypass, Flutter/React-Native RE
hypnguyen1209/offensive-claude
Stars: 421Claude CodeCodexUse when running a full red-team engagement end-to-end — initial access, persistence, privilege escalation, defense evasion, C2 infrastructure, EDR bypass, living-off-the-land
hypnguyen1209/offensive-claude
Stars: 421Claude CodeCodexUse when auditing source code for vulnerabilities — drive CodeQL/Semgrep/Joern to taint untrusted data source-to-sink across injection, memory safety, deserialization/prototype-pollution, secrets/crypto/authz/race, and supply-chain risks
hypnguyen1209/offensive-claude
Stars: 421Claude CodeCodexUse the Crossplane v2 OKF MCP server as the exclusive external knowledge source for Crossplane v2 core, API, Composition, provider, function, runtime, Upjet, security, multi-tenancy, and example facts. For an external service's behavior or security guidance, use its primary vendor documentation as defined by the evidence boundary.
jkroepke/okf-crossplane-v2
Stars: 37Claude CodeCodexProteins, drug targets and peptides. Look up protein function, location and diseases (UniProt), a drug's targets, mechanism of action and indications (ChEMBL), protein interaction partners (STRING), fetch protein sequences, compute sequence properties and align sequences (Biopython). Use for any question about targets, mechanisms, protein biology or protein/peptide sequences.
ScilifelabDataCentre/scilifelab-ai-agent-mcp-workshop-2026-11-02
Stars: 4Claude CodeCodexSmall-molecule cheminformatics with RDKit. Resolve compound names or IDs to SMILES, remove salts, compute physicochemical properties, check drug-likeness rules (Lipinski, Veber), compare structural similarity (Tanimoto) and search for substructures. Use for any question about a compound's structure, properties, drug-likeness or analogues.
ScilifelabDataCentre/scilifelab-ai-agent-mcp-workshop-2026-11-02
Stars: 4Claude CodeCodexSearch PubMed for evidence with the NCBI LitSense2 semantic-search API. Returns passages from papers with their PMIDs. Use whenever an answer needs published evidence or citations, e.g. mechanism of action, resistance, clinical findings, or PK parameters to feed into a simulation.
ScilifelabDataCentre/scilifelab-ai-agent-mcp-workshop-2026-11-02
Stars: 4Claude CodeCodexPharmacokinetic / pharmacodynamic simulation with SciPy. Concentration-time profiles for repeated oral or IV dosing (Cmax, trough, AUC, half-life, steady state), Emax effect models, dose finding, regimen comparison, loading or missed doses and custom compartment models. Use for any dosing, exposure or target-coverage question.
ScilifelabDataCentre/scilifelab-ai-agent-mcp-workshop-2026-11-02
Stars: 4Claude CodeCodexYour habits, imprinted on AI. Learns how you work from conversation, builds a portable profile, and applies judgment that adapts to you: when to act, when to check with you, when to follow the project's rules over your own defaults. Use this skill whenever the user starts a new session, opens a project, writes or reviews code, debugs, plans, or writes commits. If .dna.md does not exist yet, start the onboarding conversation before doing anything else. Active in almost every working session.
ilang-ai/Imprint
Stars: 104Claude CodeCodexDebug a reversible-circuit primitive that is value-exact in isolation but leaves identical classical, phase and ancilla dirt on every Fiat-Shamir shot once wired into the full circuit. Run a three-step falsifier ladder first: stale stream-specific optimization indexes, free-pool qubit-ID aliasing, then the measurement-vent discharge target. Use before blaming the primitive's math.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexRun production GPU jobs on Google Colab (G4 = RTX PRO 6000 Blackwell 96 GB by default; H100/A100/L4/T4 also available on a paid plan) from a local machine, with the signed-in `colab` CLI and the `colab-lane` wrapper (tools/wolkeschieber in this repository). Use when a lane needs to run, compile or benchmark something on a cloud GPU (CUDA, torch, nonce/prescreen kernels, Rust builds). Jobs run until done, then results are downloaded and the runtime is stopped. Covers spend, auth, disconnect handling and the exact failure semantics.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexAdversarial review before you commit. Before a route change, paid CPU or GPU compute, or a worker handoff, an independent worker from another lab tries to kill the route. The output is a falsifiable decision (proceed, measure, park, kill or human review) plus the hidden assumption that could make it wrong. Advisory only.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexIterate on an ecdsa.fail route until a fresh official `ecdsafail run` says it is better, never on a self-reported number, and keep a route journal (tried, killed, next cut) that survives context compaction. Use for "loop this route", "run it to a verified win", "what have I already tried". Adapted from tanweai/pua (discipline only).
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexSearch academic literature through the Elicit API: papers, clinical trials, reports, systematic reviews and Research Agent sessions. Use when a question needs published evidence or an outside, literature-backed view. Needs your own Elicit API key.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexBuild and validate a fast, exact local copy of a benchmark's official evaluator: same inputs, same counts, same score, proven by a differential fuzz test and a reproduced graded log. Use when the official judge is too slow, too memory-hungry or too opaque to sit inside the edit loop of an optimization campaign (circuits, provers, gas, proof size), when many candidates must be scored per day, or when a failure-rate estimate needs fresh samples the judge cannot give.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexBefore porting a module from another source tree, measure whether and at what cost it builds under your resource cap (fit probe), then import it verbatim through an adapter that remaps its resources and asserts its contract, instead of rewriting it. Use when a rival's or a library's routine is cheaper than yours, is self-contained, and shares your artefact's op format: a circuit gadget, a prover gadget, a contract library under a size cap.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexMaintain your contributions to a moving-leader leaderboard as an ordered stack of idempotent patches (stack/NN-slug/) that rebase onto whatever submission currently leads, with a background leader watcher, a restack that scores the leader first, and a submission gate tied to the live board (submit only when the stack beats the leader by a written margin at submission time). Use on any benchmark where rivals keep landing rows while you build.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexLand each optimization lever behind a default-on constant with an inert development override and a set of numbered deliberate breakages that the test suite must catch, so stacked levers stay separable and every check is shown to have teeth. Use when stacking more than two levers on one generator-built artefact (circuit, prover, contract, proof), when porting a lever from another tree, or when a lever's correctness rests on an invariant and not on an identity.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexUse when mapping ecdsa.fail q1152/lower peak-qubit pressure, especially Trailmix/Ludicrous fold, add, codec, and GCD phases, before editing or scaling compute.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexEvidence-discipline recovery for stalled ecdsa.fail work. Use when the same route, prompt or script has failed twice, an agent keeps tweaking parameters without changing the idea, a failure is blamed on tooling before anyone checked, a completion is claimed without validator output, or a compute request has no owner, validator, kill gate, budget or stop condition. Not for a first pass with a known fix.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexFix Python AST source-identity assertions that break across interpreter versions while keeping the exact semantic check. Keeps a source review separate from an actual fixture run.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexFor a new algorithmic design, write the exact classical reference model first and make that one model serve as test oracle, parameter-table generator, failure-class predictor, failing-case replayer and seed scanner. Use when starting a new design in a benchmark-optimization campaign (circuit, prover trace, contract, proof term) or when adopting a rival's design you will modify; not for post-passes or retunes of a design whose model already exists.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexExecutable invariant checkers for space-efficient reversible arithmetic circuits, derived from eprint 2026/2014 (Jo & Lee, exact in-place modular inversion with 3n/2+o(n) qubits). Use before an ecdsa.fail build/eval/submit, when porting a low-qubit layout (four-hole / omitted-rail ports), when deciding whether an in-place erase relation is a legal permutation, when pricing spooky-pebbled uncomputation offline against a lane budget, or when auditing a candidate circuit's peak/Toffoli/clean-ancilla structure from ops.bin. Fires on "rci", "check the layout", "is this erase legal", "price the pebble", "ops.bin census", "omitted rail audit", "exceptional set".
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexCompare baseline and candidate on identical input vectors before blaming one call for ecdsa.fail residual or eval dirt. Use when a structural edit changes the op stream, because Fiat-Shamir sampling then tests the two circuits on different shots and can create or hide failures.
odinfree/storm-ecdsa-harness
Stars: 4Claude CodeCodexGuides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexTests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexAutomates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodexConducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
nota-america/forgecat-agent-profiles
Stars: 93Claude CodeCodex