Expert Raycast extension capability skill for command design, extension architecture, testing, and store-ready publication workflows.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
3 prerequisites to line up before setup.
Safety & privacy surface
1 safety and 1 privacy notes across 2 risk areas. Review closely: credentials & tokens, network access.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
# Trigger
"Apply the Raycast extension dev/publish capability pack to this project."
# Required output
1) Extension command architecture
2) API/auth/storage approach
3) QA checklist and failure handling
4) Store publication readiness reportThis capability pack is pinned to documentation verified on 2026-04-10. When upstream docs change, refresh endpoint contracts, examples, and constraints before using this skill for production changes.
Always prefer direct retrieval from official docs/API references over model memory for limits, endpoint signatures, and behavior guarantees.
This capability pack teaches agents how to design and ship Raycast extensions that are useful in real workflows. It focuses on maintainable architecture and store submission quality.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Issue: Extension feels slow or brittle
Fix: Add caching and request timeouts with clear fallback UI states.
Issue: Store review rejects submission
Fix: Audit metadata, permissions, and UX consistency against Raycast guidelines.
Issue: External API changes break commands
Fix: Add schema guards and compatibility adapters for remote responses.
Show that Raycast Extension Dev Publish Capability Pack Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/raycast-extension-dev-publish-capability-pack)Raycast Extension Dev Publish Capability Pack Skill side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Expert Raycast extension capability skill for command design, extension architecture, testing, and store-ready publication workflows. Open dossier | Expert Raycast extension maintainer capability pack for reviewing Raycast command structure, manifest metadata, API usage, store submission checks, and privacy-safe release notes aligned to official Raycast developer docs. Open dossier | Expert Codex plugin capability pack for safe plugin scaffolding, manifest quality, MCP integration, and maintainable distribution. Open dossier |
|---|---|---|---|
| Next stepsDiffers | |||
| Trust | |||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-10 | Package not verified | Package verified2026-04-11 |
| Source provenanceDiffers | Source-backed | Submission linkedSource submission | No submission link |
| SubmitterDiffers | — | kiannidev | — |
| Install risk | Review first | Review first | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | ||
| Category | skills | skills | skills |
| Source | First-party | Source-backed | First-party |
| Author | JSONbored | kiannidev | JSONbored |
| Added | 2026-04-10 | 2026-06-15 | 2026-04-11 |
| Platforms | |||
| Harness | |||
| Source repo | — | — | — |
| Safety notes | ✓Installs from a downloaded package and may run local commands or scaffold files as part of the workflow; review the package and any generated changes before applying. | ✓This skill reviews extension behavior; it must not publish store updates or run untrusted extension code without maintainer approval. Extensions can invoke network APIs and local filesystem operations; verify least-privilege scopes before release. Do not embed long-lived API tokens in source; prefer Raycast preferences and secure storage patterns. Third-party dependencies in extensions inherit supply-chain risk; review updates before shipping. | ✓Scaffolds and validates plugin manifests and may run plugin or build commands; review generated manifests and scripts before installing or executing them. |
| Privacy notes | ✓Operates on your local project files and any context you share in the session; review what you expose before sharing — nothing is sent beyond the model unless a step calls an external service. | ✓Raycast extensions may read clipboard, local files, or user preferences depending on API usage. Network calls can transmit query text, auth tokens, and user identifiers to third-party services. Store release notes should not include internal API keys, employee data, or customer examples. Telemetry or analytics SDKs require explicit disclosure in extension README and store metadata. | ✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts. |
| Prerequisites |
|
|
|
| Install | | — | |
| Config | — | — | — |
| Citations | |||
| Claim | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.