Agent skill

Free Tier Strategy

by sickn33 in sickn33/agentic-awesome-skills

Design free tiers that convert to paid without creating resentment or abuse.

MITAuto-check passed

Install Free Tier Strategy

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill free-tier-strategy -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sickn33/agentic-awesome-skills free-tier-strategy --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/free-tier-strategy .claude/skills/free-tier-strategy && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
free-tier-strategy
GitHub stars
47k
Used in
1 other repo
Token cost
~3.4k tokens
SKILL.md length
1,425 words
Files
2
Skills in repo
1,497
Repo updated
First seen
Licence
MIT

At a glance

Design free tiers that convert to paid without creating resentment or abuse.

  • Works in 4 steps: Allow meaningful usage - Build and run a… → Cover hobbyist use cases - Personal… → Trigger on growth, not time - Upgrades… → …
  • Phrases: free tier design
  • SKILL.md covers When to Use, Overview, Before You Start and Free Tier vs Free Trial vs…, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Free Tier Strategy is an agent skill from sickn33/agentic-awesome-skills. Design free tiers that convert to paid without creating resentment or abuse. Trigger phrases: free tier design, freemium model, free trial strategy, free tier limits, developer free plan, open source commercial, feature gating, upgrade triggers, free tier conversion

Its SKILL.md is about 3.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • Phrases: free tier design
  • Free trial strategy
  • Free tier limits
  • Developer free plan

Example prompts

  • “/free-tier-strategy”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Allow meaningful usage - Build and run a real side project
  2. Cover hobbyist use cases - Personal projects should never require payment
  3. Trigger on growth, not time - Upgrades happen because projects succeed
  4. Be easy to predict - Developers should know when they'll hit limits

What it can do on your machine

Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Free Tier Strategy loads about 3.4k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 1,425 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~3.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 1,425 words, ~3,443 tokens.

Download SKILL.mdSave it as .claude/skills/free-tier-strategy/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
free-tier-strategy
description
Design free tiers that convert to paid without creating resentment or abuse. Trigger phrases: free tier design, freemium model, free trial strategy, free tier limits, developer free plan, open source commercial, feature gating, upgrade triggers, free tier conversion
risk
none
source
https://github.com/jonathimer/devmarketing-skills/tree/main/skills/free-tier-strategy
source_repo
jonathimer/devmarketing-skills
source_type
community
date_added
2026-07-01
license
MIT
license_source
https://github.com/jonathimer/devmarketing-skills/blob/main/LICENSE

Free Tier Strategy

When to Use

Use this skill when you need design free tiers that convert to paid without creating resentment or abuse. Trigger phrases: free tier design, freemium model, free trial strategy, free tier limits, developer free plan, open source commercial, feature gating, upgrade triggers, free tier conversion.

Design free tiers that let developers build real things, demonstrate value, and convert naturally—without feeling like a trap or creating resentment.

Overview

Developer tools need free tiers. Developers expect to try before they buy, and they expect the trial to be meaningful—not a 14-day timer or a feature-locked demo. But free tiers also need to sustain your business. Get this wrong in either direction: too restrictive kills adoption, too generous kills revenue.

The best free tiers feel generous to individual developers while naturally scaling into paid tiers as projects grow.

Before You Start

Review the /devmarketing-skills/skills/developer-audience-context skill. Free tier design varies significantly based on whether you're targeting hobbyists, startups, or enterprises. Also understand your unit economics—what does each free user actually cost you?

Free Tier vs Free Trial vs Freemium

Definitions

Free trial: Time-limited full access (14 or 30 days)

  • Best for: High-touch enterprise sales
  • Worst for: Developer tools with self-serve motion

Free tier: Permanently free with usage/feature limits

  • Best for: Developer tools with self-serve adoption
  • Requires: Careful limit design

Freemium: Free tier plus premium features for payment

  • Best for: Tools with clear hobby/pro distinction
  • Requires: Obvious value in premium features

Open core: Free open source with commercial additions

  • Best for: Infrastructure and platforms
  • Requires: Active open source community
Choosing Your Model
FactorFree TrialFree TierFreemiumOpen Core
Sales motionHigh-touchSelf-serveSelf-serveMixed
Time to evaluateWeeksMonthsMonthsUnlimited
Conversion pressureHighLowMediumNone
Community buildingLowMediumMediumHigh
Support costsHighLowMediumVariable

Developer tools almost always need a permanent free tier, not a free trial. Developers build side projects, evaluate tools for future use, and recommend tools to others—all of which require long-term free access.

Usage Limits That Make Sense

Good Limit Dimensions

API calls/requests

  • Developers understand and can track
  • Scales naturally with application growth
  • Example: 10,000 requests/month

Compute resources

  • Clear relationship to cost
  • Predictable for developers
  • Example: 500 build minutes/month

Storage

  • Easy to understand
  • Natural upgrade trigger as data grows
  • Example: 1GB storage

Seats/users

  • Makes sense for collaboration tools
  • Natural upgrade for team growth
  • Example: Up to 3 team members
Bad Limit Dimensions

Time-based trials disguised as free tiers

  • "Free tier expires after 90 days of inactivity"
  • Creates anxiety and resentment

Arbitrary feature combinations

  • "Free: 3 projects with 2 environments each, max 5 databases per environment, 100MB per database"
  • Too complex to evaluate

Limits that punish success

  • "Free up to 100 monthly active users"
  • Your most successful free users hit limits fastest
The Goldilocks Zone

Free tier limits should:

  1. Allow meaningful usage - Build and run a real side project
  2. Cover hobbyist use cases - Personal projects should never require payment
  3. Trigger on growth, not time - Upgrades happen because projects succeed
  4. Be easy to predict - Developers should know when they'll hit limits
Example: Good Limit Structure

Vercel:

  • Unlimited personal projects
  • 100GB bandwidth/month
  • Serverless function limits
  • Hobby use stays free forever

Supabase:

  • 500MB database storage
  • 2GB bandwidth
  • 50,000 monthly active users
  • Social auth unlimited

PlanetScale:

  • 1 database
  • 1 billion row reads/month
  • 10 million row writes/month
  • 5GB storage

Feature Gating Strategies

The Free Features Principle

Free tiers should include everything needed to:

  1. Evaluate the product thoroughly
  2. Build and ship a real project
  3. Operate in production at small scale
Features to Keep Free
  • Core functionality
  • All integrations and SDKs
  • Standard authentication
  • Basic monitoring and logs
  • Documentation and community support
  • Development and testing environments
Features to Gate Behind Paid Tiers

Collaboration features:

  • Team members beyond the solo developer
  • Access controls and permissions
  • Audit logs

Scale and performance:

  • Higher rate limits
  • More compute/storage
  • Premium infrastructure (dedicated instances)

Enterprise requirements:

  • SSO/SAML
  • SLAs and uptime guarantees
  • Priority support
  • Compliance certifications
  • Custom contracts
Feature Gating Anti-Patterns

Gating basic developer needs:

Bad: Custom domains require paid plan
(Custom domains are table stakes)

Bad: CI/CD integration requires paid plan
(This is how developers deploy)

Bad: Environment variables limited on free
(This is basic functionality)

Gating that breaks evaluation:

Bad: "Advanced features" available for 7 days then locked
(Developers can't properly evaluate)

Bad: Production deploys require credit card
(Can't demonstrate to stakeholders)

Avoiding "Free Tier Tax" Resentment

What Creates Resentment
  1. Hidden degradation - Free tier is slower, less reliable
  2. Feature removal - Features moved from free to paid
  3. Surprise limits - Hitting limits without warning
  4. Contemptuous messaging - "Upgrade to unlock BASIC features"
  5. Support discrimination - Free users treated as second-class
Creating Positive Free Tier Experience

Clear expectations:

Free tier includes:
- Everything you need to build and launch
- No credit card required
- No time limits

Upgrade when you need:
- Team collaboration
- Higher usage limits
- Priority support

Graceful limit handling:

You've used 8,000 of 10,000 free API calls this month.

Options:
- Wait for reset on March 1st
- Upgrade to Pro ($29/mo) for 100,000 calls
- Request temporary limit increase (for launches)

Honest feature comparisons: Don't artificially cripple free tier to make paid look better.

The GitHub Model

GitHub's free tier evolution shows how to do this well:

  1. Free private repos (previously paid)
  2. Free CI/CD minutes for public repos
  3. Free Copilot for open source maintainers
  4. Generous free tier for organizations

Result: Developers love GitHub, happily pay when they need more.

Upgrade Triggers and Timing

Natural Upgrade Triggers

Growth triggers:

  • Hit usage limits (bandwidth, storage, API calls)
  • Add team members
  • Create more projects/environments
  • Need more history/retention

Maturity triggers:

  • Move to production
  • Need uptime SLA
  • Require compliance
  • Want premium support
Trigger Communication

Bad: Nagging

[Popup every login]
Upgrade to Pro! 50% off this week only!
[Dismiss] [Upgrade]

Good: Contextual

[When approaching limits]
You're at 85% of your free tier API calls.
Your current usage suggests you'll hit the limit in 3 days.

[View usage] [Explore plans]

Better: Helpful

[When adding 4th team member]
Free tier includes 3 team members.

To add more collaborators, upgrade to Team ($25/user/mo).
This includes: [benefits relevant to teams]

[Not now - stay with 3] [Upgrade to Team]
Show full SKILL.md (587 more words)Show less
Timing Principles
  1. Never interrupt workflow - Don't block actions with upgrade prompts
  2. Warn before limits - 70%, 85%, 95% notifications
  3. Explain the trigger - "You're seeing this because..."
  4. Offer alternatives - Not just "upgrade or suffer"
  5. Remember choices - Don't repeat dismissed prompts daily

Open Source + Commercial Models

The Open Core Model
Open Source (MIT/Apache)          Commercial
─────────────────────────────────────────────────
Self-hosted core                  Cloud hosting
Community support                 Priority support
Standard features                 Enterprise features (SSO, audit)
                                  Compliance and SLAs
Making Open Core Work

Clear boundary: Developers should know exactly what's open source and what's commercial.

Good example (GitLab):

  • Community Edition: Complete Git platform
  • Enterprise Edition: Advanced security, compliance
  • SaaS: Managed hosting with CE or EE features

Open source must be useful: The open source version should be genuinely useful, not crippled. Developers will notice and resent "open-source-washing."

Commercialization Strategies

Cloud vs self-hosted:

  • Open source: Self-host for free
  • Commercial: Managed cloud hosting
  • Example: Plausible, Metabase, Supabase

Enterprise features:

  • Open source: Complete for individual/small team
  • Commercial: SSO, audit logs, compliance
  • Example: GitLab, Sourcegraph

Support and SLA:

  • Open source: Community support
  • Commercial: Priority support, uptime SLA
  • Example: Most open source databases
Community Relationship

Do:

  • Contribute genuinely to open source
  • Accept community contributions
  • Maintain transparency about commercial decisions
  • Offer free commercial tier for open source projects

Don't:

  • Relicense or change terms suddenly (see HashiCorp, Redis, Elastic)
  • Compete with community-built features by commercializing them
  • Use open source primarily as marketing
  • Ignore community feedback on commercial boundaries

Pricing Page Communication

Show Limits Clearly
Free                    Pro ($29/mo)           Enterprise
─────────────────────────────────────────────────────────
10,000 API calls        100,000 API calls      Unlimited
1GB storage             50GB storage           Unlimited
3 team members          25 team members        Unlimited
Community support       Email support          Priority + SLA
FAQ Free Tier Questions

Every pricing page needs:

  • "Is the free tier actually free forever?"
  • "What happens when I hit limits?"
  • "Can I use free tier for commercial projects?"
  • "Do I need a credit card for free tier?"
Pricing Page Examples

Excellent: Vercel

  • Clear free tier description
  • Per-feature limit comparison
  • Usage calculator
  • "Hobby" framing (not "limited")

Excellent: Supabase

  • Generous free tier prominent
  • Clear limit numbers
  • Feature comparison table
  • Open source status visible

Examples: Free Tiers That Work

Stripe
  • No monthly fee for free tier
  • Pay only on transactions (2.9% + 30¢)
  • Test mode unlimited and forever
  • Full feature access
  • Why it works: Aligns cost with revenue
Cloudflare
  • Generous free tier (unlimited bandwidth)
  • Premium features clearly differentiated
  • Free tier is genuinely useful for most sites
  • Why it works: Free users become advocates
MongoDB Atlas
  • 512MB storage free forever
  • Shared cluster (good enough for learning)
  • All features available to test
  • Why it works: Devs learn on free, companies pay
Algolia
  • 10,000 records free
  • 10,000 search requests/month
  • Full API access
  • Why it works: Scales with application success

Examples: Free Tier Problems

Anti-Pattern: The Hidden Trial

"Free tier" that expires after 90 days of inactivity, or reduces limits after initial period.

Anti-Pattern: The Feature Prison

Core features locked behind payment, making free tier useless for evaluation.

Anti-Pattern: The Support Desert

Free users get AI chatbot only, can't access any human help even for bugs.

Anti-Pattern: The Sudden Rug Pull

Previously free features moved behind paywall without grandfathering.

Tools

Usage Tracking and Limits
  • Lago - Open source usage-based billing
  • Metronome - Usage metering and billing
  • Orb - Usage-based billing platform
  • Stripe Billing - Metered billing support
Feature Flags for Gating
  • LaunchDarkly - Feature flag management
  • Flagsmith - Open source alternative
  • PostHog - Feature flags with analytics
Analytics for Conversion
  • Amplitude - Track free-to-paid conversion
  • Mixpanel - Funnel analysis
  • ProfitWell - SaaS metrics and pricing
  • /devmarketing-skills/skills/usage-based-pricing - Pricing models for developer tools
  • /devmarketing-skills/skills/developer-signup-flow - Getting developers to free tier
  • /devmarketing-skills/skills/developer-onboarding - Activating free tier users

Limitations

  • Use this skill only when the task clearly matches its upstream source and local project context.
  • Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
  • Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/free-tier-strategy of sickn33/agentic-awesome-skills.

  • SKILL.md
  • README.md

Open the folder on GitHubat commit b84d35a

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Free Tier Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Free Tier Strategy compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Free Tier Strategy this skillsickn33/agentic-awesome-skills47k1 repos~3.4kAutomated safety check: PassMIT
Convertremotion-dev/remotion63k—~247Automated safety check: PassCustom licence
Word to Markdown Convertergithub/awesome-copilot40k—~1.6kAutomated safety check: PassMIT
Paid Adsnowork-studio/notfair-plugin3.9k—~250Automated safety check: PassMIT
Paid Creative AItech-leads-club/agent-skills7k—~6.4kAutomated safety check: PassCustom licence
A-Share Convertible Bond AnalysisHKUDS/Vibe-Trading35k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Convert

    remotion-dev/remotion

    Official

    Start the local @remotion/convert app and open it in the Codex browser.

    63k GitHub stars~247 tokensUpdated yesterday
    Media & CreativeAuto-check passed
  • Word to Markdown Converter

    github/awesome-copilot

    Official

    Converts Word .docx files to Markdown with a bundled script before analysis, extracting embedded images and handling whole folders alongside the PDF and Excel converters.

    40k GitHub stars~1.6k tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed
  • Paid Ads

    nowork-studio/notfair-plugin

    Coordinate safe, evidence-based paid-media work across Google Ads, Meta Ads, X Ads, LinkedIn Ads, Reddit Ads, TikTok Ads, Amazon, and ChatGPT Ads.

    3.9k GitHub stars~250 tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Paid Creative AI

    tech-leads-club/agent-skills

    When the user wants to create AI-generated ad creative, test performance creative, manage creative fatigue, or optimize paid media with AI tools.

    7k GitHub stars~6.4k tokensUpdated 2 days ago
    Marketing & SEOAuto-check passed
  • Analyzes Chinese A-share convertible bonds with a three-part valuation, clause game analysis, the double-low strategy and a rotation framework for choosing bonds; instructions are in Chinese.

    35k GitHub stars~1.1k tokensUpdated today
    Business, Finance & HRAuto-check passed
  • Convert Plaintext To Md

    github/awesome-copilot

    Official

    Convert a text-based document to markdown following instructions from prompt, or if a documented option is passed, follow the instructions for that option.

    40k GitHub starsUsed in 1 repo~2.8k tokens
    Documents & OfficeAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,497 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Free Tier Strategy

What does Free Tier Strategy do?

Design free tiers that convert to paid without creating resentment or abuse. Free Tier Strategy is an agent skill from sickn33/agentic-awesome-skills. Design free tiers that convert to paid without creating resentment or abuse.

When should I use Free Tier Strategy?

Free Tier Strategy fits situations like: phrases: free tier design; free trial strategy; free tier limits; developer free plan.

How do I install Free Tier Strategy in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill free-tier-strategy -a claude-code`. Or copy the skill folder (skills/free-tier-strategy in sickn33/agentic-awesome-skills) into .claude/skills/free-tier-strategy in your project. Claude Code loads it when a task matches its description.

How do I install Free Tier Strategy in Codex?

Run `npx skills add sickn33/agentic-awesome-skills --skill free-tier-strategy -a codex`. Or copy the skill folder (skills/free-tier-strategy in sickn33/agentic-awesome-skills) into .agents/skills/free-tier-strategy in your project. Codex loads it when a task matches its description.

Can I use Free Tier Strategy in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill free-tier-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/free-tier-strategy, .gemini/skills/free-tier-strategy, .github/skills/free-tier-strategy and .opencode/skills/free-tier-strategy in your project.

What does Free Tier Strategy need to run?

SKILL.md names no scripts, command-line tools or credentials: Free Tier Strategy is instructions for the agent only.

Does Free Tier Strategy access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Free Tier Strategy safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Free Tier Strategy use?

Free Tier Strategy is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Free Tier Strategy use?

About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Free Tier Strategy?

Skills that share tags, products or a category with Free Tier Strategy: Convert (remotion-dev/remotion, 63k stars), Word to Markdown Converter (github/awesome-copilot, 40k stars), Paid Ads (nowork-studio/notfair-plugin, 3.9k stars) and Paid Creative AI (tech-leads-club/agent-skills, 7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Free Tier Strategy?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.

Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.