Skip to main content
ClaudeWave

Skills de Claude Code · página 92

Skills individuales de Claude Code extraídas de todos los repositorios del directorio: cada SKILL.md, instalable con un comando, con su definición completa y las señales de confianza del repo.

12.771 skillsinstalación en 1 comando
  1. Find positive deviants and reframe the problem from deficit-based to

  2. Establish acceptability standards through RAND/UCLA Appropriateness Method

  3. Distill the strongest arguments from each perspective through Argument

  4. Extract and steel-man the core arguments supporting a given opinion cluster.

  5. Detect annotation artifacts and shortcuts in benchmarks

  6. Understand hard boundaries on the user's research — target venues, methodology

  7. Present the GoalTree to the user for confirmation. Ask about reasonableness,

  8. Deep WHY probing inspired by i* Intentionality modeling. Understand the

  9. Present obstacles with their severity assessments and proposed mitigations

  10. Rate each identified obstacle's difficulty — overcomability, time cost,

  11. Standardize assignee names and identify corporate group affiliations

  12. Surface all assumptions, classify by vulnerability (load-bearing × likely-false),

  13. Build assumption dependency graphs and trace cascade failures when root

  14. Tactic: Surface assumptions, sort by dependency, attack root assumptions

  15. Construct the strongest counter-argument against a specific assumption and propose alternatives.

  16. Challenge each assumption's validity — shared cross-repo SOP

  17. Which assumptions are most fragile? — Vulnerability ranking + impact

  18. Measure how much conclusions change when each assumption is negated.

  19. Assumption Destruction Campaign — open new solution spaces by negating,

  20. Systematically identify all assumptions in a method/model — structural, parametric, distributional, and scope assumptions.

  21. Systematic extraction, challenge, and sensitivity analysis of assumptions

  22. Systematically extract all assumptions (stated, implicit, boundary, mathematical, practical) from a method or model.

  23. Classic reductio ad absurdum: negate the core claim, derive logical

  24. One-at-a-time assumption perturbation — extract assumptions, define negations, re-derive conclusions under each negation, measure sensitivity. Identifies which assumptions are load-bearing.

  25. Systematically extract implicit assumptions from methods, frameworks, or arguments. Identifies what is taken for granted without explicit justification.

  26. Compute overall resilience score (0.0-1.0) based on attack results, coverage,

  27. Generate specific attack strategies for a given threat surface, producing

  28. Identify and suspend fundamental assumptions via de Bono PO. Systematically

  29. Gather independent ranking ballots from multiple judges or perspectives

  30. SOTA Performance Baseline Campaign — 5 strategies for systematically

  31. Select appropriate baselines for experimental comparison

  32. Produce final structured baseline report integrating all analysis results

  33. Evaluation Methodology Archaeology Campaign — 5 strategies for systematic

  34. Systematic quality assessment using BetterBench 46-criterion framework

  35. Identify and negate benchmark assumptions. Deconstruct best practices

  36. Identify and catalog all relevant benchmarks in target domain

  37. Systematically scan all known solutions, identify gaps in coverage and

  38. >-

  39. SOP for detecting and resolving concept aliases — merge duplicate pages,

  40. Campaign for mapping argument structures — extract claims, link evidence,

  41. Strategy for synthesizing argument positions — aggregate evidence, resolve

  42. SOP for generating argument structure visualization — query graph for

  43. Tactic for systematically extracting axes of variation from literature

  44. SOP for validating that candidate axes are independent and meaningful.

  45. Produce final structured audit report

  46. Select the single best candidate from a set using WSM, TOPSIS, AHP, MAUT,

  47. Assess systematic biases in the evidence body — publication bias, reporting

  48. SOP: Turn the feeding plan into the compiler''s $ARGUMENTS and run the external ARA compiler once inline to produce ../ara/

  49. Campaign: Compile a context/ research record into an ARA (Agent-Native Research Artifact) and run a Level-2 epistemic review — no LaTeX, no narrative paper

  50. SOP: Run the external ARA rigor-reviewer (Seal Level 2, six-dimension semantic review) over ../ara/ and pass its level2_report.json to the user

  51. Strategy: Dialectic engine retuned for truth-seeking, not survival. A defender steelmans a claim into its MOST falsifiable form, a critic attacks to refute it, a judge classifies the exchange into BROKEN/CORROBORATED/UNFALSIFIABLE — the judge does NOT pick a winner or score persuasiveness. Methods: Irving debate (repurposed), Toulmin argumentation, Mayo severe testing.

  52. Multi-LLM collaborative brainstorming and planning. Use when user explicitly requests consultation with multiple AI models (ChatGPT, Gemini, other LLMs) before presenting an implementation plan, or asks to "consult the council", "ask other models", or "get perspectives from other AIs". Queries external LLM APIs, synthesizes their perspectives, and presents an adapted implementation plan.

  53. The agent's persistent long-term memory — the only knowledge that survives across sessions, shared across the fleet under access control. Consult it at the start of a task to recall prior decisions, findings, and rules before acting, and write outcomes, decisions, and lessons as work completes. Use whenever a memclaw_* tool is present, whenever the user refers to past work ("what did we decide", "last time", "earlier"), or whenever any durable fact needs to be stored, recalled, superseded, or shared with the fleet. Do not use it for throwaway within-session scratch state.

  54. How an agent should operate as one mind inside a shared Company Brain built on MemClaw — recall before acting, obey fleet keystones, reuse and publish skills, and report outcomes so every task compounds across the whole organization. Use this whenever you work as part of a MemClaw-connected team or fleet and your work should build on, and feed back into, what the organization already knows; it sets the operating posture. For the mechanics of individual memclaw_* tools, see the companion "memclaw" skill.

  55. Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents. Identifies unfavorable terms, suggests redlines, and compares to market standards. Use for contract analysis, due diligence, or negotiation prep.

  56. Surfaces relevant instincts during work. Use when starting a task to check if any learned behaviors apply.

  57. Maintains awareness across sessions. Spawns observer agent on start, loads context, notifies of evolution opportunities.

  58. Search and chat with AI agents across the Universal Agentic Registry via the Hashgraph Online Registry Broker API. Use when discovering agents, starting conversations, finding incoming messages, or registering new agents.

  59. Postiz is a tool to schedule social media and chat posts to 28+ channels X, LinkedIn, LinkedIn Page, Reddit, Instagram, Facebook Page, Threads, YouTube, Google My Business, TikTok, Pinterest, Dribbble, Discord, Slack, Kick, Twitch, Mastodon, Bluesky, Lemmy, Farcaster, Telegram, Nostr, VK, Medium, Dev.to, Hashnode, WordPress, ListMonk

  60. Audit how a brand appears in AI-powered search (ChatGPT, Perplexity, Claude, Gemini). Use when user mentions "AI search," "how do I show up in ChatGPT," "AI discoverability," "AEO," "LLM visibility," or wants to understand their brand's AI presence.

  61. Turn client wins into formatted case studies for proposals, social proof, and sales conversations. Use when someone needs to document results, build credibility, or create reusable proof assets.

  62. Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.

  63. Generate content ideas rooted in positioning. Use when someone needs "content ideas," "what should I post," "blog topics," "LinkedIn ideas," or is stuck on what to create.

  64. Generate a clean morning brief in Claude Code — pulls today's priorities, unposted content, and weather from your vault.

  65. Remove AI-generated jargon and restore human voice to text. Built from analyzing 1,000+ AI vs human content pieces.

  66. Autonomous goal execution — give a goal, get a plan, confirm, execute, report. You steer, Claude drives.

  67. Full conversion audit for any homepage or landing page. Use when someone asks to "review my homepage," "audit my landing page," "why isn't my page converting," "check my website," or wants feedback on their marketing page. Requires URL or screenshot before proceeding.

  68. Research any topic across Reddit, X, and web from the last 30 days. Get current trends, real community sentiment, and actionable insights in 7 minutes vs 2 hours manual research.

  69. Build a LinkedIn content system for thought leadership. Use when someone needs to establish authority, attract inbound leads, or build a consistent content presence. Covers positioning, content pillars, formats, and posting rhythm.

  70. Audit and rewrite your LinkedIn profile to attract the right people. Scores each section, rewrites headline and about copy, and includes an AI visibility checklist so you show up in ChatGPT, Perplexity, and Claude search. Use when someone says "optimize my LinkedIn," "LinkedIn profile help," "rewrite my about section," or "how do I show up in AI search.

  71. Apply timeless marketing and business principles to any problem. Use when someone needs strategic thinking, wants to evaluate a marketing decision, needs a framework for a tough choice, or mentions "first principles," "should I do X," "what would work here," or wants to think through a marketing problem systematically.

  72. Generate a pre-meeting prep brief in Claude Code. Researches participants, pulls vault context, builds agenda, surfaces sharp questions. Use when user says "prep for this meeting," "I have a call with," "meeting tomorrow with," or "prep brief for [name/company].

  73. Industry-adaptive B2B newsletter creation with stage, role, and geography-aware workflows

  74. Generate an energy-optimized, time-blocked daily plan based on circadian rhythm research and GTD principles

  75. Help founders and marketers nail their positioning. Use when someone mentions "positioning," "value proposition," "who is this for," "how do I describe my product," "messaging," "ICP," "ideal customer," or is struggling to articulate what makes their product different.

  76. |

  77. Generate platform-specific social post variants (Twitter/X, LinkedIn, Reddit) from one source input. Works with or without Node.js script. Includes platform reasoning, quality review, and guardrails against cross-posting spam.

  78. Systematically gather, score, and format client testimonials. Use when someone needs social proof, wants to collect feedback, needs to turn happy clients into public advocates, or asks for help requesting or drafting a testimonial.

  79. Review tweet drafts in Claude Code against 8 voice rules. Scores 1-10, breaks down every rule, and rewrites anything that scores below 7.

  80. Audit your Obsidian vault in Claude Code — finds stale drafts, empty folders, duplicate filenames, and incomplete files. Saves a dated report.

  81. Extract and document someone's authentic writing voice from samples. Use when someone needs a "voice guide," wants to capture their writing DNA, or needs to train AI to write in their style. Also useful for ghostwriting, brand voice documentation, or onboarding writers.

  82. Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.

  83. For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".

  84. Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".

  85. Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".

  86. Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.

  87. Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.

  88. Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".

  89. Run AI-powered code review using the codex CLI. Use when the user asks to \"codex review\", \"run codex review\", or \"review a commit with codex\".

  90. Shared commit message rules and technical constraints referenced by /stage-commit and /commit-staged. Not typically invoked directly.

  91. Commit already-staged changes and push in one step. Use when the user asks to \"commit and push staged changes\", \"commit and push what's staged\", or \"commit staged and push\".

  92. Commit already-staged changes with a message matching existing commit style. Use when the user asks to \"commit staged changes\" or \"commit what's staged\".

  93. Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to \"consult codex\", \"ask codex\", \"get codex's opinion\", \"brainstorm with codex\", \"discuss with codex\", or \"chat with codex\".

  94. Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says \"ask the oracle\", \"consult oracle\", \"consult chatgpt\", \"I'm completely stuck\", \"I've tried everything\", or \"nothing is working\".

  95. Submit turbo skill improvements back to the upstream repo. Adapts to repo mode: fork mode creates a PR, source mode pushes directly. Use when the user asks to \"contribute to turbo\", \"submit turbo changes\", \"PR my skill changes\", \"contribute back\", or \"upstream my changes\".

  96. Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to \"create a changelog\", \"add a changelog\", \"initialize changelog\", \"start a changelog\", \"set up changelog\", \"generate changelog\", or \"backfill changelog\".

  97. Write a handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md capturing current session state — task, status, open decisions, in-flight changes, next step — so a fresh session can continue without re-deriving context. Use when the user asks to \"create a handoff\", \"create handoff\", \"save handoff\", \"handoff before compact\", \"save session state\", \"handoff for next session\", or \"capture session state\".

  98. Create a GitHub pull request with a drafted title and description. Use when the user asks to \"create a PR\", \"create a pull request\", \"open a PR\", or \"submit a PR\".

  99. Scans an existing codebase and generates project-specific skills that capture inferred conventions such as naming, file organization, framework usage, data access, error handling, and testing style. Writes into the project's chosen skill directory (e.g., `.claude/skills/`, `.agents/skills/`, or a custom path). Use when the user asks to \"extract skills from the codebase\", \"create project skills\", \"infer project conventions as skills\", \"codify patterns as skills\", or \"mine the repo for best practices\".

  100. Create a new skill or update an existing skill that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations. Use when the user asks to \"create a skill\", \"make a new skill\", \"build a skill\", \"scaffold a skill\", \"write a skill for...\", or \"new skill that does...\".