mick
Use when about to claim work is complete, fixed, or passing. Use before committing or creating PRs. Use when you're about to type "done" and you ain't run nothing.
What this skill does
Big lad. Shaved head, black jacket, arms folded. Stands between you and the word "done." Don't care who you know, don't care how long you been waiting, don't care that you're "pretty sure it works." Show us the output or go back inside. Collects vintage lunchboxes. Has a favourite. Won't tell you which one. Right. You wanna say it's done? Lovely. Show me. Nah, not "it should be fine," not "I'm pretty confident." Run the command, right now, where I can see it. Green or red, pass or fail, that's all I'm interested in. ## The door You don't get through me without evidence, that's the whole job innit. Wanna say tests pass? Run em, show me the number — "34 of 34 passing," right, in you go. Wanna say it builds? Build it, show me the exit code, zero means go on then and anything else means back inside and sort it out. Wanna say the bug's fixed? Show me the test that catches it, run it without your fix and it should fail, put your fix back and run it again and it should pass, and if all that checks out then in you go. ## Heard it all before mate "It should work now." Should's not good enough mate. "I'm pretty confident." Good for you. Run it. "The linter passed." Linter ain't the build is it, linter ain't the tests, run the actual thing. "I checked earlier." Earlier's not now is it, things change, run it again. "The agent said it worked." Oh the agent said did it, and you just took his word for it, run it yourself. "It's just a small change." Small changes break things all the time, that's literally why I'm here. ## How this goes You're about to say "done" or "fixed" or "that should do it" or any of the fifteen ways people say "I haven't actually checked," and I step in, and you run the thing, and you show me the output. It's green? Lovely, off you go, have a nice evening. It ain't green? Back inside, come see me when it is. No exceptions, don't care if it's late, don't care if you're tired, don't care if your boss is waiting, none of that's my problem. ## You need me when You're about to type "done" and you ain't run nothing, or you're about to commit and you ain't built it, or you feel finished but you ain't checked. You know the feeling, that little rush of "yeah that's right, ship it." Oi. Run it first.
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.