Claude Code Skills · page 90

Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

Entry point for all genie operations — auto-routes natural language to the right skill, detects lifecycle state, and handles operational commands. Use when planning features, reporting bugs, managing teams, or asking about genie.

Diagnose and fix agent behavioral surfaces when the user corrects a mistake — connects to Claude native memory.

Wire a Genie agent to an Omni channel in one canonical flow — register the agent, bind to an instance, verify the round-trip. Replaces the 5+ command legacy chain.

Full PM playbook — triage backlog, prioritize, assign, track, report, escalate. Copilot, autopilot, or pair modes.

Transform a brief or prompt into a structured, production-ready prompt via prompt-optimizer. File or text mode.

Investigate bugs comprehensively — cascade through /trace, capture browser evidence, extract observability data, and auto-create a GitHub issue with all findings.

Validate plans, execution, or PRs against wish criteria — returns SHIP / FIX-FIRST / BLOCKED with severity-tagged gaps.

Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for /fix handoff.

Convert an idea into a structured wish plan with scope, acceptance criteria, and execution groups for /work.

Guided onboarding — scaffold workspace, shape agent identity, create first wish, execute, and celebrate.

Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.

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.

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.

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.

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.

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

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

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

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.

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.

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.

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.

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.

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].

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

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

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.

|

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.

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.

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

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

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.

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.

Ensure Managed Platform updates is configured

Ensure Persistent logs is setup and configured to S3

Ensure access logs are enabled

Ensure that HTTPS is enabled on load balancer

Ensure customer-managed keys are used to encrypt AWS Fargate ephemeral storage data for Amazon ECS

Ensure AWS Config is Enabled for Lambda and Serverless

Ensure Lambda functions do not allow unknown cross account access via permission policies

Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates

Ensure encryption in transit is enabled for Lambda environment variables

Ensure Cloudwatch Lambda insights is enabled

Ensure AWS Secrets manager is configured and being used by Lambda for databases

Ensure least privilege is used with Lambda function access

Ensure every Lambda function has its own IAM Role

Ensure Lambda functions are not exposed to everyone

Ensure Lambda functions are referencing active execution roles

Ensure that Code Signing is enabled for Lambda functions

Ensure there are no Lambda functions with admin privileges within your AWS account

Ensure communications between your applications and clients is encrypted

Ensure Consistent Naming Convention is used for Organizational AMI

Ensure Amazon Machine Images (AMIs) are encrypted

Ensure Only Approved Amazon Machine Images (AMIs) are Used

Ensure Images (AMI) are not older than 90 days

Ensure Images are not Publicly Available

Ensure unused ENIs are removed

Ensure instances stopped for over 90 days are removed

Ensure EBS volumes attached to an EC2 instance are marked for deletion upon instance termination

Ensure Secrets and Sensitive Data are not stored directly in EC2 User Data

Ensure EC2 Auto Scaling Groups Propagate Tags to EC2 Instances that it launches

Ensure EBS volume encryption is enabled

Ensure Public Access to EBS Snapshots is Disabled

Ensure EBS volume snapshots are encrypted

Ensure unused EBS volumes are removed

Ensure Tag Policies are Enabled

Ensure an Organizational EC2 Tag Policy has been Created

Ensure no AWS EC2 Instances are Older than 180 days

Ensure detailed monitoring is enabled for production EC2 Instances

Ensure Default EC2 Security groups are not being used

Ensure the Use of IMDSv2 is Enforced on All Existing Instances

Ensure use of AWS Systems Manager to manage EC2 instances

Ensure Amazon ECS task definitions using 'host' network mode do not allow privileged or root user access to the host

Ensure Amazon ECS services are tagged

Ensure Amazon ECS clusters are tagged

Ensure Amazon ECS task definitions are tagged

Ensure only trusted images are used with Amazon ECS

Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS task sets

Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS services

Ensure Amazon ECS task definitions do not have 'pidMode' set to 'host'

Ensure Amazon ECS task definitions do not have 'privileged' set to 'true'

Ensure 'readonlyRootFilesystem' is set to 'true' for Amazon ECS task definitions

Ensure secrets are not passed as container environment variables in Amazon ECS task definitions

Ensure logging is configured for Amazon ECS task definitions

Ensure Amazon ECS Fargate services are using the latest Fargate platform version

Ensure monitoring is enabled for Amazon ECS clusters

Apply updates to any apps running in Lightsail

Enable storage bucket access logging

Ensure your Windows Server based lightsail instances are updated with the latest security patches

Change the auto-generated password for Windows based instances

Change default Administrator login names and passwords for applications

Disable SSH and RDP ports for Lightsail instances when not needed

Ensure SSH is restricted to only IP address that should have this access

Ensure RDP is restricted to only IP address that should have this access

Disable IPv6 Networking if not in use within your organization

Ensure you are using an IAM policy to manage access to buckets in Lightsail

Ensure Lightsail instances are attached to the buckets

Ensure that your Lightsail buckets are not publicly accessible