Use when discovering, loading, creating, or improving a reusable Signalsurf Workspace custom Skill, or when deciding whether instructions belong in a Skill instead of Memory, Knowledge, Project Context, or a resource.
Installs into .claude/skills of the current project.
Are you the author of Custom Skills?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/signalsurf-ai-custom-skills)
---
name: custom-skills
description: Use when discovering, loading, creating, or improving a reusable Signalsurf Workspace custom Skill, or when deciding whether instructions belong in a Skill instead of Memory, Knowledge, Project Context, or a resource.
---
# Signalsurf Custom Skills
Before every request using this Skill, follow [version check and automatic update](../signalsurf/references/freshness.md), then use the current guidance.
Read the [shared operating contract](../signalsurf/references/operating-contract.md) unless already loaded; a focused Skill uses the same context, actor, confirmation and result rules.
A Skill is a reusable procedure: how to perform a repeatable class of work. It is not authorization and must not hold customer facts, secrets, raw transcripts, temporary state, or one Project's current hypothesis.
## Discover and load
1. Call `skill_query` action `list`, then match the current request against each returned `When to use` description.
2. Load the complete instructions for one matching Skill by its stable id before planning or acting. Do not load every Skill or treat a catalogue description as the instructions.
3. If no Skill matches, continue using the official product Skill and live capability discovery.
## Create
Create only when the user wants to preserve a repeatable Workspace procedure. Draft sections named **Name**, **When to use**, and **Instructions**, then call `skill_manage` action `create`. If the tool returns `confirmation_required`, show that exact preview and follow the root Skill's same-conversation confirmation flow. One conversation never silently becomes a Skill.
## Update
Load the current custom Skill and `revision`, show the proposed change, and call `skill_manage` action `update` with that exact `expectedRevision` so concurrent changes fail closed. If the tool returns `confirmation_required`, follow the root Skill's same-conversation confirmation flow. Official Plugin Skills are immutable and cannot be shadowed or edited through this lifecycle.
If custom Skill query/manage capabilities are unavailable, say so and keep the draft in the conversation; do not claim it was installed or modify Plugin files as a substitute.
