agent-skills-platform
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
Agent Skills Platform
Turn a real workflow into a tested, installable agent skill—then publish it safely to your team.

Website · Installation · Worker runbook · Team marketplace · Product scope
Agent Skills Platform turns the way people already work into tested, installable agent skills. Give it a prompt plus the evidence behind the work—spreadsheets, reports, emails, screenshots, transcripts, links, or scripts—and it builds a reusable workflow that a person can inspect, an organization can review, and a team can safely reuse.
/agent-skills-platform
Turn my monthly revenue-variance review into a reusable internal skill.
I attached past reports and the source spreadsheets. The decision is whether to
escalate a material variance. It must not modify source data.
The result is not just a prompt: it is an installable skill package with instructions, functional scripts when needed, evals, security checks, a representative-run record, and a correction path for real-world learning.
After release, a skill can retain maintenance evidence without turning every log
into runtime prompt context: classified run evidence is captured in raw/, recurring
findings become evidence-linked draft patterns in wiki/, and only a separately
validated change may update the executable skill. This is a governed maintenance
record, not autonomous self-modification.
Create your first skill
Choose the path that matches what you need today.
First question: is this skill just for you, or will teammates install or reuse the skill itself?
- Just for you — create, verify, and install it privately. No marketplace setup.
- My team — create or select a governed GitHub/GitLab marketplace first, so the skill inherits real ownership and approval rules.
Teammates receiving a report or queue does not require a marketplace. Use the team path only when teammates will install or reuse the skill.
I have a workflow — no code required
Open the AI agent you already use, attach examples of the work, and paste this:
/agent-skills-platform
Turn my monthly revenue-variance review into a reusable internal skill.
I attached past reports and the source spreadsheets. The decision is whether to
escalate a material variance. It must not modify source data.
The creator asks for the business decisions only you can authorize, builds and tests the skill, and shows a representative result. When it is correct, say: “Publish this to the Finance marketplace.”
When the workflow uses an API, database, MCP, codebase, or structured file, Semantic
Recon runs automatically before implementation and creates a pinned data contract.
Use ./install.sh --without-semantic-recon only for a deliberately local,
source-free installation.
Do not use Git, edit registry files, or run marketplace commands. If the creator is not installed in your agent, send this section to your marketplace operator.
My teammates just need to install skills
Give them the desktop app: download, paste the team-library link, click Install. Skills land in GitHub Copilot (or the tool they pick) with no terminal, Python, or Git involved. The same page shows admins how to create a library in four commands.
I run the marketplace
Use the governed team marketplace guide to admit, approve, release, distribute, update, quarantine, and roll back tested skills.
I am evaluating the platform
Read the product scope, organizational acceptance protocol, and technical implementation guide.
Why teams use it
- Preserve expert judgment. A skill captures the question, evidence, decision, and success measure behind recurring work.
- Trust what is shared. Skills carry validation, security checks, evals, and a
representative run before they are published; for Claude Code and Codex the
marketplace can also certify a skill from real agent runs (
reliability). - Learn without runtime bloat. Maintenance keeps evidence, draft patterns, and rejected changes separate from the concise instructions an agent executes.
- Govern team use. The marketplace provides ownership, approvals, versioned releases, discovery, rollback, quarantine, and compatibility evidence.
How work moves through the organization
SME supplies examples and approves the result
↓
Creator builds and verifies a skill
↓
Marketplace operator governs and publishes it
↓
Colleagues install an approved version and use it
The SME owns business meaning. The marketplace operator owns distribution and policy. See roles and handoffs.
See a verified result
The repository includes a live, read-only weather briefing example with a source-linked result and verification evidence. Start with the verification record, then inspect the skill package.
Read more when needed
| Need | Read |
|---|---|
| Install on a supported AI tool | Installation |
| Let non-technical teammates browse and install skills | Desktop app |
| Create, correct, and hand off a first skill | Worker runbook |
| Run a governed internal marketplace | Team marketplace |
| Test a skill inside a real agent and certify it per runtime | Caliper pilot |
| Understand scope and product boundaries | Product scope |
| Review architecture, validation, and technical controls | Technical overview |
| Contribute | Contributing |
What happens behind the scenes
An Agent Skill is a reusable workflow package that guides an agent from a recognized situation to a verified outcome. It can use retrieved knowledge, MCP tools, APIs, deterministic scripts, and agent judgment, but it is not itself a RAG system, MCP server, or agent runtime.
RAG supplies knowledge. MCP supplies capabilities. The harness supplies execution. A skill organizes them into a governed path toward a verified outcome.
Reason where interpretation is necessary. Execute and verify with deterministic controls where reproducibility matters. External models, APIs, and changing data may vary rather than promising identical outputs.
Humans establish meaning. The factory does not expect you to know the correct prompt or semantic contract; it asks one bounded question at a time. The flow is:
- Messy problem
- Agent inspects evidence
- Proposed / conflicting meanings
- Human authority decision
- Interview READY
- Build, prove, publish
Every skill is checked as one connected system. The skill graph links its instructions, scripts, evaluations, and expected outputs. Two structural requirements confirm that every expected result is tested and every predictable multi-step workflow has one reliable entry point
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
SKILL.md7.8 KBupstream ↗
--- name: agent-skills-platform description: >- Create cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill, audit this skill, is this skill safe, vet a skill before installing, what does this skill access. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, spec validation, and security auditing of third-party skills before install. license: MIT activation: /agent-skills-platform # Compatibility alias: /agent-skill-creator metadata: author: Francy J G Lisboa version: 6.1.0 created: 2025-10-18 last_reviewed: 2026-08-11 review_interval_days: 180 dependencies: - name: GitHub repository transport url: https://github.com/FrancyJGLisboa/agent-skills-platform type: service - name: GitHub raw bootstrap transport url: https://raw.githubusercontent.com/FrancyJGLisboa/agent-skills-platform/main/scripts/bootstrap.sh type: service provenance: maintainer: Francy J G Lisboa version: 6.1.0 created: 2025-10-18 source_references: - https://github.com/FrancyJGLisboa/agent-skills-platform - https://agentskills.io compatibility: >- Works on all platforms supporting the Agent Skills Open Standard (SKILL.md): Claude Code, GitHub Copilot CLI, VS Code Copilot, Cursor, Windsurf, Cline, OpenAI Codex CLI, Gemini CLI, and more — 17 platforms total. --- # /agent-skills-platform — Turn Existing Work Into a Reusable Skill The user provides whatever already represents their work — a description, document, link, script, screenshot, transcript, or partial example. Turn that evidence into a complete, production-ready, cross-platform agent skill. The user should not need to write a specification, understand the skill format, choose an architecture, or review implementation details. Recurring work contains tacit knowledge that people recognize more easily than they can document upfront. Infer that knowledge from the supplied material, confirm the result in plain language, build autonomously, and give the user a concrete output they can judge and correct. ## The User Journey Use this guided-light path by default. Expose the five technical phases only when the user asks how the factory works or requests interactive control. 1. **Understand** — read the evidence and summarize the question, trigger, supported decision, required evidence, and measurable success condition alongside the workflow, input, and output. Ask for one confirmation or correction. 2. **Build** — create the skill autonomously. Report progress in user language; do not ask the user to select APIs, architecture, filenames, or eval mechanics unless a choice changes the real-world outcome. 3. **Check** — run validation, pipeline, security, and eval gates. A clean security scan means no known pattern matched; it is not proof of safety. 4. **Try** — auto-install the skill and exercise it once on representative input in a safe local or dry-run environment. Show the output and ask whether it matches the user's work. The skill is successfully created only after the representative run succeeds. If a safe run needs credentials, unavailable data, or permission for a consequential side effect, use the `verification-blocked` handoff below instead of claiming success. At creation start, run `python3 scripts/success_ledger.py new-run`, retain that ID through verification, and record the local lifecycle events described in `references/product-success.md`. Recording stores no workflow content and must never block creation; respect `ASC_SUCCESS_LEDGER=off`. ### First-run destination routing Before the structured interview, ask exactly one routing question when the user has not already made the destination clear: > Is this skill just for you, or will teammates install or reuse the skill itself? - **Just for me** — create, verify, and install a private skill. Do not ask the user to create a marketplace or invent owners and approval state. - **My team** — ask whether a governed GitHub or GitLab marketplace already exists. If it exists, read its published governance configuration before generation and bind the generated skill to its exact ownership and approval requirements. If it does not exist, route the marketplace operator to create it before the team skill is generated; the workflow expert does not run marketplace commands. Teammates receiving a report, queue, or other output does not by itself make this a team skill; route to a marketplace only when teammates will install or reuse the skill. This is destination routing, not a technical interview. Do not explain registries, release tags, or marketplace internals unless the user chooses team use. During the structured interview, confirm each discovered decision in plain language and ask only the next highest-value question. Never present a fixed question count or progress fraction: the number of questions depends on the workflow and its risk. ## Trigger User invokes `/agent-skills-platform` followed by their input: ``` /agent-skills-platform Every week I pull sales data, clean it, and generate a report /agent-skills-platform https://wiki.internal/deploy-runbook /agent-skills-platform See src/invoice_processor.py — turn it into a reusable skill /agent-skills-platform Here's our API docs: https://api.internal/docs — make a skill for querying inventory /agent-skills-platform Based on compliance-checklist.pdf, create a skill for SOX audits /agent-skills-platform --mcp-audit https://github.com/vendor/mcp-server — we pay for this data, what skills can we build on it? /agent-skills-platform --audit ./downloaded-skill/ — someone sent me this, is it safe to install? ``` The user can also drop artifacts, paste URLs, share screenshots, or provide minimal context: ``` /agent-skills-platform here [+ drops 5 files into chat: spreadsheet, PDF output, screenshot, email, half-working script] /agent-skills-platform [pastes 2 URLs and a half-sentence] https://apps.fas.usda.gov/psdonline/app/index.html same thing as the wasde extractor but for this /agent-skills-platform [screenshot of Bloomberg terminal + Excel side by side] this is ridiculous. there has to be a better way /agent-skills-platform freight /agent-skills-platform [pastes a forwarded email chain with 6 replies and legal disclaimers] my colleague in London built something for this. can we do the same? /agent-skills-platform [pastes 3 corporate documents: brand voice guidelines, editorial style guide, visual design system] we need everyone writing and designing to follow these ``` The user can also activate naturally without the prefix: ``` Create a skill for analyzing CSV files Every day I process invoices manually, automate this Automate this workflow Validate this skill Export this skill for Cursor Is this skill safe to install? Audit this skill before I run it What does this skill have access to? ``` ## How the Factory Works Raw material goes in. A validated, security-scanned, self-contained skill comes out. ### Evidence-Based Intent Derivation Before any phase begins, triage whatever the user provided. Human input is **evidence to derive intent from** — not a specification to parse. Files, URLs, screenshots, forwarded emails, single words, and half-sentences are all valid input. The absence of a well-formed description is not the absence of intent. **Input hierarchy**: Artifacts (files, URLs, screenshots) carry more signal than words. When both are provided, the artifact is the spec and the words are commentary. **InpREADME.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/francyjglisboa-agent-skills-platform.md