Foundatio
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
$ npx skills add fossasia/eventyay --skill stripe-projects -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fossasia/eventyay stripe-projects --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/stripe-projects .claude/skills/stripe-projects && rm -rf skills-srcUse ~/.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/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .claude/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projectsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add fossasia/eventyay --skill stripe-projects -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fossasia/eventyay stripe-projects --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/stripe-projects .agents/skills/stripe-projects && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .agents/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fossasia/eventyay --skill stripe-projects -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fossasia/eventyay stripe-projects --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/stripe-projects .cursor/skills/stripe-projects && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .cursor/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/fossasia/eventyay.git --path .agents/skills/stripe-projects--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add fossasia/eventyay --skill stripe-projects -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fossasia/eventyay stripe-projects --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/stripe-projects .gemini/skills/stripe-projects && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .gemini/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install fossasia/eventyay stripe-projectsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add fossasia/eventyay --skill stripe-projects -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/stripe-projects .github/skills/stripe-projects && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .github/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add fossasia/eventyay --skill stripe-projects -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install fossasia/eventyay stripe-projects --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fossasia/eventyay.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/stripe-projects .opencode/skills/stripe-projects && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stripe-projects" agent skill from https://github.com/fossasia/eventyay/tree/dev/.agents/skills/stripe-projects into .opencode/skills/stripe-projects/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stripe-projects", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
stripe-projectsA skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects.
Stripe Projects is an agent skill from fossasia/eventyay. Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set up monitoring", "show me the catalog", "what can I provision", "browse providers", "add an LLM provider", "configure model provider", "add email sending", "set up search", "add a message queue"…
Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Event-driven systems, Transactional email and File uploads and storage. It works with Stripe, PostgreSQL and Redis. The repository describes itself as: Open Source Event Management, Ticketing and Checkins, Talks and Schedules, Video and Interpretations, Badges, Exhibitions and more https://eventyay.com. The licence is Apache-2.0.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit b539d59. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
Bash(stripe *)Bash(which stripe)Bash(brew install stripe/stripe-cli/stripe)Bash(brew upgrade stripe/stripe-cli/stripe)SkillReadFrom allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
stripebrewFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.stripe.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
ENV_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Stripe Projects loads about 2k tokens when it runs. Until then it costs about 234 tokens; SKILL.md has 859 words of instructions outside code blocks.
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.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
state under `.projects/` and generates `.env` files. Don’t hand-edit these files. If you need to inspect project state,Only inspect `.projects/` or `.env` directly if the user explicitly asks you to — the CLI is authoritative, so manual edAutomated 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.
The full file from fossasia/eventyay at commit b539d59, republished under its Apache-2.0 licence (© fossasia). 859 words, ~2,021 tokens.
.claude/skills/stripe-projects/SKILL.md (or your agent's skills folder).Provision third-party services (databases, auth, hosting, analytics, caching, AI, observability) and retrieve API keys/tokens using the Stripe Projects CLI plugin.
Check if the Stripe CLI is available:
which stripe && stripe --versionIf not installed or below version 1.40.0:
brew install stripe/stripe-cli/stripe (or brew upgrade stripe/stripe-cli/stripe)Then ensure the Projects plugin is installed:
stripe plugin install projectsConfirm the requested provider/service exists:
stripe projects search <query> --jsonIf result_count is 0, inform the user the service was not found and stop.
If the user’s request is vague (for example, “I need a database”), browse the catalog to suggest options:
stripe projects catalog --jsonCheck if a project is already initialized:
stripe projects status --jsonIf not initialized, run a preflight check first to reveal all blockers at once:
stripe projects init --preflight --jsonIf all preflight checks pass, or the only failure is TOS_ACCEPTANCE_REQUIRED, proceed:
stripe projects init --accept-tos --yesIf any check fails with BROWSER_AUTH_REQUIRED, PROJECTS_SESSION_UNUSABLE, or ACCOUNT_NOT_ELIGIBLE, stop here. Report that check’s message and remedy to the user verbatim and let them resolve it — clearing these requires a browser sign-in or a Dashboard visit you cannot perform. Do not run stripe projects init yourself and do not re-run the preflight: neither clears the blocker for you, since only the user can complete a browser sign-in or a Dashboard step.
Follow the remedy the failing check prints rather than assuming stripe login is the fix. If a Stripe CLI session already exists, stripe login reports that you are already logged in and exits 0 without changing anything — an exit code of 0 from a login command does not mean the blocker cleared.
Important: stripe projects init installs the stripe-projects-cli skill locally at .claude/skills/stripe-projects-cli. This skill contains the full post-init command reference.
Verify the skill was installed:
test -f .claude/skills/stripe-projects-cli/SKILL.md && echo "OK" || echo "MISSING"If MISSING: re-run stripe projects init --accept-tos --yes once — the skill is bundled with the Projects plugin and installed during init. If the file is still missing after that single retry, or if init exits non-zero, report init’s error message to the user and stop. Do not keep re-running init.
If OK: use the locally-installed stripe-projects-cli skill (invoke using the Skill tool with name stripe-projects-cli) to continue the workflow — adding services, managing credentials, and configuring the project.
After a successful service addition, provide output in this format:
| Field | Value |
|---|---|
| Provider | <provider name> |
| Service | <service type> |
| Tier | <tier> |
| Env vars | <variable names only — never values> |
Then suggest 3–5 complementary services from different categories in the catalog (for example, if user added a database, suggest auth, hosting, or observability). Only reference services that actually appear in stripe projects catalog --json output — never fabricate commands or provider names.
The CLI manages all state under .projects/ and generates .env files. Don’t hand-edit these files. If you need to inspect project state, use the appropriate CLI command:
| Task | Command |
|---|---|
| View provisioned services | stripe projects status --json |
| List env var names | stripe projects env --json |
| Check project health | stripe projects status --json |
| Browse available services | stripe projects catalog --json |
Only inspect .projects/ or .env directly if the user explicitly asks you to — the CLI is authoritative, so manual edits may be overwritten.
Use project variables when the user wants to store an environment variable that doesn’t come from a provisioned provider resource, such as an app URL, feature flag, or self-managed API key.
Create or update a project variable for the active environment:
stripe projects variables set <name> --env-key <ENV_KEY> --value <value>A successful variables set syncs the active environment output file immediately. If the user doesn’t provide the value, run the command without --value only in interactive mode so the CLI can prompt securely. Never print secret values in your response.
Bind an existing project variable to the active environment:
stripe projects env add <name> --variable --env-key <ENV_KEY>Remove a variable binding from the active environment without deleting the stored variable:
stripe projects env remove <name> --variableList and delete project variables:
stripe projects variables list --json
stripe projects variables delete <name> --yes| Error code | Cause | Recovery |
|---|---|---|
BROWSER_AUTH_REQUIRED | No Stripe session and browser sign-in needed | Tell the user to run stripe projects init themselves, in a terminal where they can finish the browser sign-in — you cannot fix this, and re-running it yourself will not clear it |
PROJECTS_SESSION_UNUSABLE | A Stripe CLI session exists, but Projects cannot read live-mode credentials from it | Report the message and remedy verbatim and stop. Do NOT retry, and do NOT run stripe login — it reports you are already logged in and exits 0 |
ACCOUNT_NOT_ELIGIBLE | Account not onboarded for Projects | Tell the user to run stripe projects switch-account to choose an account, or continue setup for this account; report the remedy the CLI printed and stop |
TOS_ACCEPTANCE_REQUIRED | Developer or provider terms not accepted | Re-run with --accept-tos |
PROVIDER_NOT_LINKED | Provider requires OAuth linking | Run stripe projects link <provider> — may open a browser |
PLAN_REQUIRED | Deployable needs a plan provisioned first | Provision the plan listed in the error, then retry |
UNKNOWN_ERROR | Unexpected failure | Show the full error message to the user and suggest running with --debug for diagnostics |
| Service not in catalog | Query returned 0 results | Inform user; suggest stripe projects catalog --json to browse alternatives |
| CLI not found | Stripe CLI not installed | Install using Homebrew (macOS) or follow https://docs.stripe.com/stripe-cli/install |
© fossasia, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/stripe-projects of fossasia/eventyay.
Open the folder on GitHubat commit b539d59
We found 10 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 5 other GitHub owners. This page covers the copy in fossasia/eventyay, which our catalogue first saw on October 7, 2026.
Stripe Projects 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stripe Projects this skillfossasia/eventyay | 1.7k | 5 repos | ~2k | Automated safety check: Notes | Apache-2.0 | |
| FoundatioFoundatioFx/Foundatio | 2.1k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Create Environmentgodatadriven/whirl | 205 | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Use Sealoshashgraph-online/awesome-codex-plugins | 1.3k | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| Redis Patternsaffaan-m/ECC | 276k | 1 repos | ~3k | Automated safety check: Pass | MIT | |
| Amazon Elasticacheaws/agent-toolkit-for-aws | 2.8k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 |
FoundatioFx/Foundatio
A skill your agent uses when working with Foundatio infrastructure abstractions for .NET -- caching, queuing, messaging, file storage, distributed locking, or background jobs.
godatadriven/whirl
Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.
hashgraph-online/awesome-codex-plugins
Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision…
affaan-m/ECC
Redis data structure patterns, caching strategies, distributed locks, rate limiting, pub/sub, and connection management for production applications.
aws/agent-toolkit-for-aws
Activate when developers have latent caching needs: slow API responses, database read bottlenecks, DynamoDB throttling or cost, RDS/Aurora scaling pressure, Bedrock latency or cost, or adding a…
cohen-liel/hivemind
Redis caching and queue patterns. An agent skill from cohen-liel/hivemind.
fossasia/eventyay
A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.
fossasia/eventyay
A skill your agent uses when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform…
fossasia/eventyay
Steps for initiating the Django development server without Docker
fossasia/eventyay
Docker Compose, container services, deployment. An agent skill from fossasia/eventyay.
fossasia/eventyay
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents)…
fossasia/eventyay
Repository layout and where to find code. An agent skill from fossasia/eventyay.
Works with
Categories
A skill your agent uses when the user wants to provision infrastructure or third-party services using Stripe Projects. Stripe Projects is an agent skill from fossasia/eventyay. Use when the user wants to provision infrastructure or third-party services using Stripe Projects.
Stripe Projects fits situations like: the user wants to provision infrastructure; third-party services using Stripe Projects; the user asks how to get an API key; credentials for any third-party service — dont tell them to sign up manually.
Run `npx skills add fossasia/eventyay --skill stripe-projects -a claude-code`. Or copy the skill folder (.agents/skills/stripe-projects in fossasia/eventyay) into .claude/skills/stripe-projects in your project. Claude Code loads it when a task matches its description.
Run `npx skills add fossasia/eventyay --skill stripe-projects -a codex`. Or copy the skill folder (.agents/skills/stripe-projects in fossasia/eventyay) into .agents/skills/stripe-projects in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add fossasia/eventyay --skill stripe-projects -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stripe-projects, .gemini/skills/stripe-projects, .github/skills/stripe-projects and .opencode/skills/stripe-projects in your project.
Going by SKILL.md and its folder, Stripe Projects needs the command-line tools its instructions call (stripe and brew) and credentials named ENV_KEY. Our summary lists: A credential in ENV_KEY. Its frontmatter pre-approves these tools: Bash(stripe *), Bash(which stripe), Bash(brew install stripe/stripe-cli/stripe), Bash(brew upgrade stripe/stripe-cli/stripe), Skill, Read.
SKILL.md names 1 domain. As links in the text: docs.stripe.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Stripe Projects is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2k tokens (SKILL.md is roughly 8.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Stripe Projects: Foundatio (FoundatioFx/Foundatio, 2.1k stars), Create Environment (godatadriven/whirl, 205 stars), Use Sealos (hashgraph-online/awesome-codex-plugins, 1.3k stars) and Redis Patterns (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
fossasia (a GitHub organization) maintains it in fossasia/eventyay, which has 1,702 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 9, 2026.
Source: fossasia/eventyay on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.