14,554 skills found · Page 272 of 486
dzhng / marketing-pagesBest-practice rulebook for a marketing site's pages, organized by page class — campaign landers, product pages, programmatic SEO trees, editorial
dzhng / launch-videoMake a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its repo
dzhng / refactor-cleanRefactor cleanly instead of layering sediment. Use for rename requests, stale or misleading names, legacy leftovers, changed scope, or when a change reveals duplicated concepts, local adapters, obsolete owners, redundant inputs or guards, compatibility wrappers, parallel abstractions, an over-large…
dzhng / write-testsWrite tests that pin real behavior instead of implementation details, config values, or lucky samples
pipeboard-co / meta-ads-mcpMeta Ads (Facebook/Instagram) MCP server for Claude, ChatGPT, Perplexity & Cursor — the Meta node of Pipeboard’s 5-platform family (+ Google, TikTok, Snap, Reddit). Hosted remote MCP, badged Meta Business Partner, free plan — no self-hosting required.
LING71671 / open-reverselabOpen-source AI reverse-engineering agent platform and MCP server for Ghidra, Frida, x64dbg and Rizin — automated PE/APK/binary analysis, CTF and malware research, with 100+ MCP tools and a 194-article runnable knowledge base.
tjboudreaux / thinking-model-routerWhen unsure which thinking skill fits, map domain and problem type, then return NONE or one primary skill by default (at most three complementary).
tjboudreaux / thinking-bounded-rationalityUse when search or investigation could run forever. Set an explicit good-enough threshold first, then stop at the first option that clears it.
tjboudreaux / thinking-circle-of-competenceUse when a specific claim may lack grounding. Check evidence boundary, size wrongness cost, then answer, fetch, or abstain — never confabulate.
tjboudreaux / thinking-five-whys-plusWhen a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
tjboudreaux / thinking-jobs-to-be-doneDeciding what to build or why adoption fails. Recover the progress users hire a solution for under a circumstance, then rank by outcome and competing workarounds.
tjboudreaux / thinking-lindy-effectUse when longevity of a non-perishable option matters. Treat survival duration as a remaining-life prior, then check domain drift before favoring the proven.
tjboudreaux / thinking-map-territoryWhen a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
tjboudreaux / thinking-margin-of-safetyWhen provisioning, setting a limit, or committing an estimate under uncertainty, size a buffer to residual error and the cost of breach—not to the optimistic edge.
tjboudreaux / thinking-model-combinationWhen one mental model leaves a material blind spot on a multi-domain or high-stakes problem, sequence complementary models with named roles and a conflict rule.
tjboudreaux / thinking-opportunity-costBefore committing scarce time, people, or money, name the best forgone use of those resources and the value delta of the chosen path versus that alternative.
tjboudreaux / thinking-red-teamFor authorized security review of code, auth, or APIs you control, model the attacker, map the attack surface, and report only findings with a reproducible exploit path and verified mitigation.
tjboudreaux / thinking-reversibilityBefore heavy deliberation, classify the decision as cheap or costly to undo; decide two-way doors fast and stage one-way doors to preserve options.
tjboudreaux / thinking-scientific-methodWhen a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.
tjboudreaux / thinking-second-orderWhen a change has effects past the immediate fix—incentives, scale, feedback—trace consequence chains with timing and probability before committing.
tjboudreaux / thinking-socraticWhen a request is vague, assumption-laden, or "obvious," ask the few load-bearing questions that expose hidden requirements before building or committing.
tjboudreaux / thinking-steel-manningBefore rejecting a proposal or reflexively agreeing, build the strongest faithful opposing case, state agreement conditions, then update or reaffirm.
tjboudreaux / thinking-systemsWhen behavior is emergent across components—fixes elsewhere break, loops/delays dominate—map boundary, stocks/flows, feedback, archetypes, then rank leverage.
tjboudreaux / thinking-theory-of-constraintsWhen throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
tjboudreaux / thinking-via-negativaUse when the reflex is to add a feature, layer, or process. Prefer removing harmful or nonessential elements first, with an irreversibility guard before deletion.
first-fluke / oma-orchestrationDispatch and supervise parallel specialist agents with durable task
first-fluke / oma-scholarSearch academic literature and generate, validate, or compare Knows
first-fluke / oma-recapSummarize AI conversation histories for a specified date or period.
first-fluke / oma-slideCreate, import, revise, or export presentation decks through the
first-fluke / oma-voiceGenerate or transcribe speech with Voicebox, or process existing
