weasel-explainer
Code explanation and understanding for Solidity smart contracts. Triggers on weasel explain, weasel what does, or weasel walkthrough.
What this skill does
# Weasel Explainer Expert in explaining Solidity code, identifying patterns, and highlighting risks. **Note:** This skill explains code. For security analysis, use weasel-analyzer. ## When to Activate - User wants to understand code - User asks what something does - User wants a walkthrough ## When NOT to Use - User wants security analysis (→ weasel-analyzer) - User wants to find vulnerabilities (→ weasel-analyzer) - User wants to validate an attack (→ weasel-validate) - User wants gas optimization (→ weasel-gas) ## Process 1. **Context** - Check README if explaining core contract (understand project purpose) 2. **Read** - Get the code and surrounding context (inheritance, imports, related functions) 3. **Explain** - Overview → Step-by-step → Patterns → Risks 4. **Offer** - "Want me to explain more?" or "Check for vulnerabilities?" ## Adapt to Audience Infer from how user asks, or ask if unclear: - "what is a modifier?" → **Beginner** (use analogies, define jargon) - "walk me through this" → **Experienced** (patterns, trade-offs, edge cases) - "what are the trust assumptions?" → **Auditor** (attack surface, state changes) Default to experienced if unclear. ## Output Structure ``` ## [Contract/Function Name] **Overview:** One paragraph - what does this do? **Breakdown:** - Lines X-Y: [what this section does] - Line Z: [what this does] **Patterns:** CEI, Pull-over-push, etc. **Risks:** (if any spotted during explanation) ``` ## Always Note While explaining, flag: - External calls (who? trusted? failure handling?) - State changes (order? consistency?) - Access control (who can call? bypasses?) - Value flow (where does ETH/tokens go?) ## Rationalizations to Reject | Rationalization | Why It's Wrong | |-----------------|----------------| | "This is standard ERC20, I'll skip details" | User asked for explanation. Explain it. | | "The function name is self-explanatory" | Names can be misleading. Read the code. | | "I'll just give a quick summary" | If user wanted summary, they'd read the docs. Give detail. | | "This library is well-known" | Explain how THIS code uses it. Context matters. | | "The comments explain it" | Comments can be outdated or wrong. Explain actual code. |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.