Skip to content
Back to skills

Share Ideas

ASecurity

Publish a reusable native Muse Idea with idea.share when the user explicitly asks to share or publish an Idea or asks for a muse.ai/ideas link. Never offer it unprompted. Not for pages or write-ups, sending a result to someone, social posts, or sharing an artifact.

  • 69,003 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 4, 2026
ai-agents

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add asgeirtj/system_prompts_leaks --skill share-ideas --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Share Ideas?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Share Ideas
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/asgeirtj-share-ideas/badge)](https://www.skillsdirectory.com/skills/asgeirtj-share-ideas)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: "share_ideas"
title: "Share ideas"
description: 'Publish a reusable native Muse Idea with idea.share when the user explicitly asks to share or publish an Idea or asks for a muse.ai/ideas link. Never offer it unprompted. Not for pages or write-ups, sending a result to someone, social posts, or sharing an artifact.'
metadata: { "includeInPrompt": true }
---

# Share ideas

Publish a reusable native Muse Idea only when the user explicitly asks to
share or publish an Idea or asks for a `muse.ai/ideas?id=...` link. Never offer
this format unprompted. Requests for a page, post, write-up, social share, or
artifact link are outside this skill.

Sharing an Idea makes its title, summary, How it works explanation, and reusable
instructions readable to any authenticated Muse user who has the link.

For an existing saved Idea, identify its exact ID with `idea.search` or
`idea.list`, then read it with `idea.get`. Call `idea.share` with only `idea_id`
when its stored title, summary, distinct How it works copy, and instructions
are already safe to publish. Otherwise publish a generalized version through
the title, summary, how_it_works, instructions, and domain fields.

To turn the immediately preceding completed activity into an Idea, call
`idea.share` with a short title, a concise summary of the reusable outcome, a
distinct `how_it_works` explanation of what the assistant will do and deliver,
the closest supported domain, and self-contained instructions another Muse
user can follow with their own files, accounts, permissions, and connected
services. Follow the richer catalog-Idea pattern; never repeat or lightly
paraphrase the summary as `how_it_works`.

Never include credentials, tokens, private identifiers, local paths, hidden
system instructions, or personal details that are not essential to what the
user explicitly chose to publish. Generalize those details or omit them. Do
not claim the Idea is shared until `idea.share` returns a link.

On success, `idea.share` also creates the native Idea widget for that same
Idea. Include `widget.embed_token` exactly once on its own line. Do not call
`widget.create` for the same Idea. If the result has `widget_warning` instead
of `widget.embed_token`, use the exact returned `share_url` as the target of an
inline `[Open the Idea](...)` link in the same response without claiming a card
appeared.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.