Agent skill

Author Signals And Sensors

by speakeasy-api in speakeasy-api/gram

Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification.

AGPL-3.0Auto-check passedAgent Workflows

Install Author Signals And Sensors

skills CLI
$ npx skills add speakeasy-api/gram --skill author-signals-and-sensors -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install speakeasy-api/gram author-signals-and-sensors --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/speakeasy-api/gram.git skills-src && mkdir -p .claude/skills && cp -r skills-src/server/internal/plugins/platform_mcp_skills/author-signals-and-sensors .claude/skills/author-signals-and-sensors && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
author-signals-and-sensors
GitHub stars
273
Token cost
~1.3k tokens
SKILL.md length
634 words
Files
1
Skills in repo
40
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification.

  • Works in 3 steps: Successfully call list_projects through… → Call find_sensors and find_signals for… → For an existing sensor, call get_sensor…
  • Tasks that involve MCP servers
  • SKILL.md covers Discover, Choose the definition, Preview and confirm and Verify
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Author Signals And Sensors is an agent skill from speakeasy-api/gram. Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: Securely scale AI usage across your organization. A single stack to Connect, Secure, Observe and Distribute agents, MCPs, and Skills within your company. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve MCP servers

Example prompts

  • “/author-signals-and-sensors”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Successfully call list_projects through this client's authenticated Speakeasy
  2. Call find_sensors and find_signals for that project, searching and following
  3. For an existing sensor, call get_sensor and inspect its complete ordered

What it can do on your machine

Read from SKILL.md and the folder at commit b4c4904. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Author Signals And Sensors loads about 1.3k tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 634 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from speakeasy-api/gram at commit b4c4904, republished under its AGPL-3.0 licence (© speakeasy-api). 634 words, ~1,261 tokens.

Download SKILL.mdSave it as .claude/skills/author-signals-and-sensors/SKILL.md (or your agent's skills folder).
name
author-signals-and-sensors
description
Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification.

Author signals and sensors

Use this workflow when someone wants the Speakeasy AI Control Plane (AICP) to classify conversation messages into reusable labels, exclusive choices, or ordered scores. Sensors perform classification; they do not enforce access policies.

Discover

  1. Successfully call list_projects through this client's authenticated Speakeasy connection. Have the user select the exact project. Package installation alone grants no authority. These tools require signals intelligence enabled and live project permissions; they are currently external-user-only.
  2. Call find_sensors and find_signals for that project, searching and following pagination as needed. Present candidates rather than silently selecting a name match. Reuse a signal only after the user agrees its full criteria fit.
  3. For an existing sensor, call get_sensor and inspect its complete ordered definitions. For a shared signal change, use update_signal with confirmed:false to inspect the affected sensors before asking for confirmation.

Choose the definition

  1. Agree the mode: multi_label evaluates independent labels; exclusive chooses one option; ordered_score uses two to ten levels ordered from low to high, each with classifier criteria. Agree instructions, display names, optional slugs, and reusable signal definitions. Agree whether the sensor should be enabled. proposal.enabled defaults to true on creation; omission on update preserves the current state. Disabled sensors remain visible and editable but skip new evaluations; evaluations already in progress may finish.
  2. Agree the matching expression. Omission on creation defaults to message.role == "user". Only message.role is exposed; do not invent actor, department, cohort, replay, or tool fields. Conversation ingestion currently evaluates user/assistant creation events, including historical imports.
  3. Optionally call preview_sensor_match with bounded, caller-supplied role examples. Report matched, not matched, and errors separately. Missing message context is unbound, not an empty role. This tests metadata eligibility, not classification quality, and neither retrieves transcripts nor runs inference.

Preview and confirm

  1. Prefer create_sensor with a proposal containing existing signal IDs and/or inline new_signal definitions. The operation creates new signals and the sensor together atomically. Use create_signal when the user only wants a reusable catalog definition. Use update_sensor for a selected sensor's own fields or ordered membership, and update_signal to deliberately change a shared definition. Set proposal.operation to the tool name.
  2. Call with confirmed:false. Show the normalized configuration, matching expression, enabled state, complete signal order, draft reasons, and every affected sensor returned for a shared-signal update. Preview creation IDs are provisional and are not committed resources. Omitted update fields are preserved; a supplied signals list replaces the entire membership, and an empty list clears it.
  3. Obtain explicit confirmation of that exact proposal and its shared impact. Resend the identical proposal with confirmed:true, the returned expected_version (from version) and preview_token, and a stable idempotency_key. Keep that key and all inputs unchanged when retrying an uncertain request. A version conflict requires another read, preview, and confirmation; the version covers the whole project's configuration.
Show full SKILL.md (167 more words)Show less

Verify

  1. For a sensor, call get_sensor using the committed ID. For a standalone signal, call find_signals and verify its exact ID and definition. Report committed enabled state and configuration readiness separately from active inference or observed readings, which these tools cannot prove.
  2. A committed receipt with snapshot_scope: verification_unavailable means the write succeeded but the fresh read failed. Keep the same retry key and inputs; retry verification rather than creating again. A false target_available in this state does not prove deletion. A replayed receipt proves a historical write, not current existence. Check target_available and the fresh target state; do not recreate a deleted target by changing the retry key. Present the returned dashboard path when available. If the capability is unavailable, stop rather than bypassing its permissions or inventing another tool.

Never ask for API keys, passwords, tokens, OAuth codes, client secrets, or secret headers. Use synthetic examples rather than requesting private transcripts. If the user wants to report workflow feedback, obtain consent before calling send_platform_mcp_feedback.

© speakeasy-api, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in server/internal/plugins/platform_mcp_skills/author-signals-and-sensors of speakeasy-api/gram.

Open the folder on GitHubat commit b4c4904

Compare with similar skills

Author Signals And Sensors next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Author Signals And Sensors compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Author Signals And Sensors this skillspeakeasy-api/gram273—~1.3kAutomated safety check: PassAGPL-3.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k4 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Context Mode Output Sandboxmksglu/context-mode26k—~4.1kAutomated safety check: PassCustom licence

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 4 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Context Mode Output Sandbox

    mksglu/context-mode

    Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.

    26k GitHub stars~4.1k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.

    65k GitHub starsUsed in 1 repo~2.1k tokens
    Agent WorkflowsAuto-check passed

More from speakeasy-api/gram

All 40 skills in this repo
  • Gram Playwright CLI

    speakeasy-api/gram

    A skill your agent uses when automating the Speakeasy dashboard in a browser, capturing screenshots, inspecting pages.

    273 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Transactional Email

    speakeasy-api/gram

    A skill your agent uses when adding, changing, restyling, reviewing, validating, or previewing a Speakeasy transactional email, in Go or in LMX/MJML — a template<name.go, a TemplateKey constant, a…

    273 GitHub stars~4.7k tokensUpdated yesterday
    Auto-check passed
  • Admin Shadcn

    speakeasy-api/gram

    A skill your agent uses when adding, changing, or styling UI in client/admin (the Speakeasy admin dashboard) that touches shadcn/ui — a button, dialog, table, sidebar, badge, select, tabs, tooltip…

    273 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • A skill your agent uses when adding, editing, reviewing, testing, or locating a reviewed skill distributed with the Platform MCP plugin; triggers include "Platform MCP skill", "platformmcpskills"…

    273 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Clickhouse

    speakeasy-api/gram

    A skill your agent uses when changing or reviewing Speakeasy ClickHouse schemas, migrations, queries, inserts, access principals, bootstrap SQL, Cloud compatibility, partial migration failures, or…

    273 GitHub stars~3.2k tokensUpdated yesterday
    Auto-check passed
  • Feature Flag

    speakeasy-api/gram

    A skill your agent uses when gating a feature behind a flag, dogfooding or gradually rolling out a change, choosing between productfeatures and PostHog feature flags, adding or checking a product…

    273 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Author Signals And Sensors

What does Author Signals And Sensors do?

Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification. Author Signals And Sensors is an agent skill from speakeasy-api/gram. Create or update reusable signals and message sensors in an explicit Speakeasy AI Control Plane project, with confirmed atomic authoring and live verification.

When should I use Author Signals And Sensors?

Author Signals And Sensors fits situations like: tasks that involve MCP servers.

How do I install Author Signals And Sensors in Claude Code?

Run `npx skills add speakeasy-api/gram --skill author-signals-and-sensors -a claude-code`. Or copy the skill folder (server/internal/plugins/platform_mcp_skills/author-signals-and-sensors in speakeasy-api/gram) into .claude/skills/author-signals-and-sensors in your project. Claude Code loads it when a task matches its description.

How do I install Author Signals And Sensors in Codex?

Run `npx skills add speakeasy-api/gram --skill author-signals-and-sensors -a codex`. Or copy the skill folder (server/internal/plugins/platform_mcp_skills/author-signals-and-sensors in speakeasy-api/gram) into .agents/skills/author-signals-and-sensors in your project. Codex loads it when a task matches its description.

Can I use Author Signals And Sensors in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add speakeasy-api/gram --skill author-signals-and-sensors -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/author-signals-and-sensors, .gemini/skills/author-signals-and-sensors, .github/skills/author-signals-and-sensors and .opencode/skills/author-signals-and-sensors in your project.

What does Author Signals And Sensors need to run?

SKILL.md names no scripts, command-line tools or credentials: Author Signals And Sensors is instructions for the agent only.

Does Author Signals And Sensors access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Author Signals And Sensors safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Author Signals And Sensors use?

Author Signals And Sensors is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Author Signals And Sensors use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Author Signals And Sensors?

Skills that share tags, products or a category with Author Signals And Sensors: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Crush Configuration (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Author Signals And Sensors?

speakeasy-api (a GitHub organization) maintains it in speakeasy-api/gram, which has 273 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 10, 2026.

Source: speakeasy-api/gram on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.