All authors

Claude Skills by majiayu000
github.com/majiayu00015,497 skills907 installs34,333 views
- Create Deep Research PromptGenerate a structured deep research prompt. USE WHEN the user needs to research a complex topic, market, or bug deeply. Capabilities include objective clarification, tech stack validation, and prompt generation.Votes: 0GitHub stars: 666
- StatisticianUse when selecting statistical methods, performing power analysis, guiding uncertainty quantification, or validating MCMC/Monte Carlo implementations.Votes: 0GitHub stars: 666
- The FoolUse when challenging ideas, plans, decisions, or proposals using structured critical reasoning. Invoke to play devil's advocate, run a pre-mortem, red team, or audit evidence and assumptions.Votes: 0GitHub stars: 666
- Think BrainstormGood-faith divergent brainstorming for achieving a goal. Validates assumptions, then spawns brainstormers running different techniques (first-principles, working-backwards, lateral, analogical, constraints-shift, etc.) in isolation, and synthesizes the pool into a report of standouts, reasonable ideas, and hybrid combinations. Produces feedback only — no code, no tickets, no artifacts.Votes: 0GitHub stars: 666
- Thinking ArchetypesRecognize Senge's Systems Archetypes to diagnose recurring organizational and technical problems, identify why fixes keep failing, and design interventions that address root structure.Votes: 0GitHub stars: 666
- Thinking BayesianUpdate beliefs systematically based on new evidence using probabilistic reasoning. Use when estimating probabilities, learning from data, or making decisions under uncertainty.Votes: 0GitHub stars: 666
- Thinking Bounded RationalityApply Herbert Simon's Bounded Rationality and satisficing to make good-enough decisions under real-world constraints. Use for design decisions under time pressure, recognizing cognitive limits, and setting appropriate stopping criteria.Votes: 0GitHub stars: 666
- Thinking Circle Of CompetenceKnow the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.Votes: 0GitHub stars: 666
- Thinking CynefinClassify problems by complexity domain (clear, complicated, complex, chaotic) and match approach to domain. Use for choosing methodologies, problem framing, and process design.Votes: 0GitHub stars: 666
- Thinking DebiasingSystematic checklist to identify and counteract cognitive biases in decision-making. Use before major decisions, when evaluating recommendations, or when stakes are high.Votes: 0GitHub stars: 666
- Thinking Dual ProcessApply Kahneman's Dual-Process Theory to recognize when to trust intuition vs engage deliberate analysis. Use for high-stakes decisions, error-prone contexts, or when balancing speed vs accuracy.Votes: 0GitHub stars: 666
- Thinking EffectuationStart with means, not goals; co-create with partners; leverage contingencies. Use for startup strategy, innovation projects, and uncertain/novel domains where planning is unreliable.Votes: 0GitHub stars: 666
- Thinking Feedback LoopsAnalyze systems using Donella Meadows' feedback loop framework to identify reinforcing loops, balancing loops, delays, and leverage points. Use for organizational dynamics, product growth design, debugging runaway or oscillating systems, and finding high-impact interventions.Votes: 0GitHub stars: 666
- Thinking Fermi EstimationMake order-of-magnitude estimates for unknown quantities by decomposing into known or estimable factors. Use for capacity planning, cost estimation, market sizing, and technical feasibility assessment.Votes: 0GitHub stars: 666
- Thinking First PrinciplesBreak complex problems into fundamental truths by questioning assumptions and rebuilding from irreducible components. Use for innovation, challenging status quo, or when conventional solutions fail.Votes: 0GitHub stars: 666
- Thinking Five Whys PlusEnhanced root cause analysis with explicit bias guards and stopping criteria. Use for incident post-mortems, bug investigations, and process failures where standard 5 Whys might mislead.Votes: 0GitHub stars: 666
- Thinking InversionApproach problems backward by identifying paths to failure, then systematically avoiding them. Use for risk identification, planning, and avoiding obvious mistakes.Votes: 0GitHub stars: 666
- Thinking Kepner TregoeSystematic rational process for complex problem analysis, decision making, and risk assessment. Use for high-stakes engineering decisions, root cause analysis beyond 5 Whys, and multi-factor evaluations requiring structured criteria.Votes: 0GitHub stars: 666
- Thinking Leverage PointsIdentify where small changes can have large effects using Donella Meadows' hierarchy of system intervention points. Use for strategic decisions, system optimization, and choosing where to focus engineering effort.Votes: 0GitHub stars: 666
- Thinking Lindy EffectFor non-perishable things, future life expectancy is proportional to current age. Use for technology selection, evaluating frameworks/libraries, and predicting tool longevity.Votes: 0GitHub stars: 666
- Thinking Map TerritoryRecognize limits of mental models and diagrams. Use when models diverge from reality, debugging expectation mismatches, or questioning abstraction accuracy.Votes: 0GitHub stars: 666
- Thinking Margin Of SafetyBuild in buffers for unknown unknowns and don't optimize to the edge. Use for capacity planning, deadline estimation, architecture design, and risk management.Votes: 0GitHub stars: 666
- Thinking Model CombinationCombine multiple mental models for richer analysis. Use for complex problems requiring multiple lenses, high-stakes decisions, or when single models leave blind spots.Votes: 0GitHub stars: 666
- Thinking Model RouterRoute to the right mental model based on your domain and problem type. The single entry point for all thinking skills.Votes: 0GitHub stars: 666
- Thinking Model SelectionChoose the right mental model for the problem at hand. Use when facing new problems, when current approaches fail, or when you need to match tool to context.Votes: 0GitHub stars: 666
- Thinking Occams RazorApply parsimony principle to prefer simpler explanations with fewer assumptions. Use for hypothesis selection in debugging, architecture decisions, and choosing between competing approaches.Votes: 0GitHub stars: 666
- Thinking OodaRapid decision-making loop for dynamic situations. Use for incident response, competitive scenarios, time-sensitive decisions, and situations requiring quick adaptation.Votes: 0GitHub stars: 666
- Thinking Opportunity CostEvaluate decisions by what you give up, not just what you gain. Use for resource allocation, prioritization, build vs. buy choices, and technical debt evaluation.Votes: 0GitHub stars: 666
- Thinking Pre MortemImagine a project has failed and work backward to identify why. Use at project kickoffs, before major decisions, or when optimism may be obscuring risks.Votes: 0GitHub stars: 666
- Thinking ProbabilisticExpress confidence in ranges, update predictions with new information, and track calibration over time. Use for project estimation, risk assessment, and decision making under uncertainty.Votes: 0GitHub stars: 666
- Thinking ReversibilityClassify decisions by reversibility and match decision process to decision type. Use for technology choices, architecture decisions, process changes, and hiring decisions.Votes: 0GitHub stars: 666
- Thinking Scientific MethodHypothesis → Prediction → Test → Revise with explicit falsification. Use for debugging, feature experimentation, performance investigation, and A/B testing design.Votes: 0GitHub stars: 666
- Thinking Second OrderThink beyond immediate consequences to second and third-order effects. Use for strategic decisions, policy changes, and avoiding unintended consequences.Votes: 0GitHub stars: 666
- Thinking SocraticSystematic questioning framework to deepen understanding, challenge assumptions, and uncover hidden beliefs. Use for requirements gathering, debugging, coaching, and critical analysis.Votes: 0GitHub stars: 666
- Thinking Steel ManningArgue against the strongest version of opposing positions, not the weakest. Use for design reviews, evaluating alternatives, conflict resolution, and decision validation.Votes: 0GitHub stars: 666
- Thinking SystemsAnalyze problems as interconnected systems with feedback loops, emergent behavior, and non-linear effects. Use for debugging complex systems, architecture decisions, and understanding unexpected behavior.Votes: 0GitHub stars: 666
- Thinking Theory Of ConstraintsIdentify and manage the bottleneck; improvements elsewhere don't matter until the constraint is addressed. Use for performance optimization, process improvement, and resource allocation.Votes: 0GitHub stars: 666
- Thinking Thought ExperimentTest ideas through hypothetical scenarios when empirical testing is impractical. Use for architecture evaluation, edge case analysis, ethics considerations, and strategy development.Votes: 0GitHub stars: 666
- Thinking TrizApply TRIZ (Theory of Inventive Problem Solving) methodology to resolve technical contradictions and find innovative solutions. Use for engineering design, breaking through impossible constraints, and systematic innovation.Votes: 0GitHub stars: 666
- Thinking Via NegativaImprove by removal rather than addition. Focus on what to stop doing, eliminate the negative, and subtract complexity. Use for system simplification, process improvement, and feature prioritization.Votes: 0GitHub stars: 666
- Trend Analyst Skill 404kidwiz Claude Supercode Ski 2Expert in forecasting, signal detection, and market intelligence. Specializes in time-series analysis, social listening, and predictive modeling for business trends.Votes: 0GitHub stars: 666
- Us Gov Shutdown Tracker Mann1988 Awesome Claude Skill 2Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy disruptions, (3) assess "stealth tightening" effects, (4) compare shutdown episodes across different monetary policy regimes (QE vs QT), or (5) generate liquidity stress reports with histor...Votes: 0GitHub stars: 666
- Very Long Text SummarizationSummarizes very long texts (books, handbooks, biographies, codebases) using hierarchical multi-pass extraction with cheap model armies. Produces structured knowledge maps, not just summaries.Votes: 0GitHub stars: 666
- Video ResearchResearch topics and gather content for video productionVotes: 0GitHub stars: 666
- View Results Metr Inspect Action 2View and analyze Hawk evaluation results. Use when the user wants to see eval-set results, check evaluation status, list samples, view transcripts, or analyze agent behavior from a completed evaluation run.Votes: 0GitHub stars: 666
- Wikipathways Gptomics BioskillsWikiPathways enrichment using clusterProfiler and rWikiPathways. Use when analyzing gene lists against community-curated open-source pathways. Performs over-representation analysis and GSEA for 30+ species.Votes: 0GitHub stars: 666
- Workflow Analyzer Majiayu000 Claude Skill Registr作業フローや手順を分析し、自動化可能な要素を特定する。ワークフロー分析時、自動化検討時、業務プロセス改善時、またはユーザーが作業フロー分析、自動化要素、業務手順、プロセス最適化に言及した際に使用する。Votes: 0GitHub stars: 666
- Acedatacloud Api Acedatacloud SkillsGuide for using AceDataCloud APIs. Use when authenticating, making API calls, managing credentials, understanding billing, or integrating AceDataCloud services into applications. Covers setup, authentication, request patterns, error handling, and SDK integration.Votes: 0GitHub stars: 666
- Agentuity Cli Cloud Apikey CreateCreate a new API key. Requires authentication. Use for Agentuity cloud platform operationsVotes: 0GitHub stars: 666
- Api Architect Erichowens Some Claude Skills 3Expert API designer for REST, GraphQL, gRPC architectures. Activate on: API design, REST API, GraphQL schema, gRPC service, OpenAPI, Swagger, API versioning, endpoint design, rate limiting, OAuth flow. NOT for: database schema (use data-pipeline-engineer), frontend consumption (use web-design-expert), deployment (use devops-automator).Votes: 0GitHub stars: 666