Publishing Skills

Once you have built and tested a skill, you can publish it to make it available beyond your own account. Published skills can be shared with your team, your organization, or the entire systemprompt.io community through the marketplace.

Prerequisites

• A working skill that you have tested (see Creating Skills)
• A systemprompt.io account with publishing enabled

Understanding visibility levels

Before publishing, decide who should be able to discover and use your skill:

Visibility	Who can see it	Use case
Private	Only you	Personal workflows, drafts, experiments
Team	Members of your organization	Internal company processes, shared templates
Public	Everyone on systemprompt.io	Community tools, open-source skills

You can change visibility at any time after publishing. Starting with Team visibility is a good default — it lets you gather feedback from colleagues before going public.

Step 1: Review your skill

Before publishing, verify your skill is ready:

1. Open the skill in your dashboard
2. Confirm the name and description are clear to someone seeing them for the first time
3. Check that all parameters have helpful descriptions
4. Run a final test to make sure everything works as expected

A good marketplace listing starts with a good description. Spend a minute making sure someone unfamiliar with your skill can understand what it does and when to use it.

Step 2: Publish the skill

1. Open the skill in the dashboard
2. Click Publish
3. Select your desired visibility level (Private, Team, or Public)
4. Review the skill details in the confirmation dialog
5. Click Confirm

Your skill is now published. If you selected Team or Public visibility, other users can discover it in the marketplace.

Step 3: Write a marketplace listing

For Team and Public skills, the marketplace listing is how users decide whether to install your skill. A strong listing includes:

• A clear description — What the skill does in one or two sentences
• Use cases — When someone should use this skill ("Use this to generate weekly status reports from project notes")
• Parameter explanations — What each input expects and any defaults
• Example output — A brief sample of what the skill produces (if applicable)

You can edit the listing at any time from the skill editor.

Step 4: Manage access (Team visibility)

For Team-visibility skills, access is controlled by your organization membership:

1. Go to Settings > Team in the dashboard
2. Verify that the team members who need access are part of your organization
3. All team members automatically see Team-visibility skills in their marketplace

There is nothing additional to configure. If someone joins your organization, they gain access to all Team-visibility skills immediately.

Updating published skills

Published skills can be updated at any time. When you edit and save a published skill, the changes are applied immediately to all users who have installed it.

To update a published skill:

1. Open the skill in the dashboard
2. Make your changes to the instructions, parameters, or description
3. Click Save

The updated skill syncs automatically. Users do not need to reinstall or take any action.

Version management

systemprompt.io tracks changes to your published skills so you can see the history of edits.

• Every save creates a new version in the skill history
• You can view previous versions from the History tab in the skill editor
• To revert to a previous version, open it from the history and click Restore

This makes it safe to experiment with changes. If an update produces worse results, roll back to the previous version in a few clicks.

Unpublishing a skill

If you need to remove a skill from the marketplace:

1. Open the skill in the dashboard
2. Click Unpublish
3. Confirm the action

Unpublishing sets the skill back to Private visibility. Users who previously installed the skill will no longer have access. Your skill and all its versions are preserved in your account — nothing is deleted.

Best practices

• Start with Team visibility — Get feedback from colleagues before publishing publicly
• Write descriptions for your audience, not yourself — Assume the reader has never seen your skill before
• Keep parameter names intuitive — Use topic instead of t, word_count instead of wc
• Test after every update — A small change to instructions can significantly alter output quality
• Check the marketplace periodically — See how your skill appears to others and refine the listing
• Respond to feedback — If team members report issues, iterate on the instructions and publish an update

Troubleshooting

• Publish button is grayed out — Ensure the skill has a name, description, and at least one instruction block saved
• Team members cannot see the skill — Verify they are part of your organization under Settings > Team
• Changes not reflecting for other users — Confirm you clicked Save after editing; changes sync automatically on save
• Skill showing old version — Try refreshing the marketplace page; if the issue persists, check the History tab to confirm your latest changes were saved