You probably already have skills worth selling. If you've written .cursorrules files, CLAUDE.md project configs, custom prompts, or any documented workflow that makes your AI coding agent better at a specific task, you're sitting on a sellable product. Here's how to package it.
> Quick Answer: Any documented workflow, coding convention, or AI agent configuration you've built for yourself can become a SKILL.md skill. Extract the instructions from your existing configs, structure them with YAML frontmatter, add supporting files, and publish on Agensi. The packaging process takes 15 to 30 minutes for most workflows.
What counts as a sellable skill?
If you've ever done any of the following, you already have the raw material for a skill:
Written a .cursorrules file that makes Cursor follow your team's coding standards. Written a CLAUDE.md file that onboards Claude Code to your project. Built a custom prompt that you paste into your AI agent at the start of every session. Documented a workflow in a README or wiki that you follow repeatedly. Created a script that automates part of your development process.
Any of these can be restructured as a SKILL.md and published on Agensi. The difference between a personal config and a sellable skill is generalization. Instead of referencing your specific project, you write instructions that work for any project in the same category.
How do I convert a .cursorrules file?
A .cursorrules file is always-on project context. To convert it to a SKILL.md, split it into two parts.
The general coding conventions stay in .cursorrules because they apply to every interaction. The specific workflows (code review process, testing checklist, deployment steps) become individual skills because they should only activate when needed.
For example, if your .cursorrules contains both "use TypeScript strict mode, prefer functional components" and a detailed 15-step code review checklist, the TypeScript preferences stay as .cursorrules and the code review checklist becomes a skill:
```yaml
---
name: team-code-review
description: Use when the user asks to review code, check a PR, or find bugs.
---
# Code Review Process
Review code for the following in order:
1. Security issues (hardcoded secrets, SQL injection, XSS)
2. Logic errors and edge cases
3. Error handling completeness
...
```
For a detailed comparison of the two formats, read Cursor Rules vs SKILL.md Skills.
How do I convert a CLAUDE.md file?
CLAUDE.md files serve a similar purpose to .cursorrules but for Claude Code. The conversion is the same: project-level context stays as CLAUDE.md, and specific workflows become skills.
The key question for each section of your CLAUDE.md is: "Does this apply to every interaction, or only when doing a specific task?" If it's task-specific, it's a skill.
For the full comparison, read SKILL.md vs CLAUDE.md.
How do I generalize personal configs for the marketplace?
The main change is removing project-specific references and replacing them with patterns that work across projects.
Before (personal config): "Run tests with `pnpm test -- --filter=@myapp/api`"
After (marketplace skill): "Detect the package manager (npm, pnpm, yarn) from the lockfile. Run tests using the detected package manager with the appropriate test command for the project's test runner."
Before: "Use the company design tokens from `src/styles/tokens.ts`"
After: "If the project has a design tokens file, read it first and use the project's actual tokens. If no tokens file exists, use sensible defaults following Material Design 3 conventions."
The goal is making the skill smart enough to adapt to any project instead of hardcoded to yours.
What supporting materials should I add?
Skills that include supporting files sell for two to three times more than bare SKILL.md files. Consider adding:
Reference files. A markdown file with patterns, examples, or checklists that the skill references during execution. A security audit skill might include `references/owasp-top-10.md` with the full checklist.
Scripts. Helper scripts that the skill invokes. A deployment skill might include `scripts/pre-deploy-check.sh` that validates environment variables.
Examples. A folder with example inputs and outputs so buyers can see exactly what the skill produces before they install it.
README. A README.md in the skill folder that explains what the skill does, how to use it, and any configuration options.
For more on packaging, read How to Create a SKILL.md from Scratch.
---
*Turn your configs into income. Publish on Agensi and keep 80% of every sale.*
