cipher_skill

This skill decodes user intent from vague requests by extracting context, surfacing assumptions, and producing precise, structured specifications for
  • Shell

8

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill simota/agent-skills --skill cipher

  • SKILL.md4.7 KB

Overview

This skill decodes user intent beyond surface wording and converts vague requests into precise, actionable specifications. It combines project context, conversation history, and repository signals to surface hidden assumptions and prevent misinterpretation. Use it as a gatekeeper that clarifies intent before work is started or passed to other agents.

How this skill works

Cipher gathers context from git history, project notes, and conversation logs, then synthesizes that data to infer the most likely intent. It explicitly lists assumptions, identifies implicit requirements, and either produces a structured specification or asks targeted questions when multiple interpretations could change outcomes. Outputs are formatted for downstream agents and include confidence and next steps.

When to use it

  • When a user request is vague, incomplete, or ambiguous
  • Before routing tasks to development or automation agents
  • When hidden constraints or domain assumptions may affect outcomes
  • When multiple agents need a single, authoritative interpretation
  • Prior to actions that are irreversible or high-risk

Best practices

  • Always run Cipher before task handoff to reduce rework
  • Ensure relevant context (git log, PROJECT notes, conversation) is available before invoking
  • Prefer clear, minimal assumptions and label each one explicitly
  • Use the skill’s targeted questions only at decision points that materially change outcomes
  • Treat Cipher outputs as the authoritative structured spec for downstream agents

Example use cases

  • User asks “Fix the login” — Cipher expands scope: auth flows, edge cases, and rollback plan
  • An agent returns unclear test requirements — Cipher produces precise acceptance criteria
  • Routing hub receives conflicting routing instructions — Cipher synthesizes intent and recommends the safest path
  • Preparing a change that could delete data — Cipher flags high-risk actions and asks required confirmations
  • Transforming a product request into developer tasks with prioritized, measurable specs

FAQ

Cipher needs project context: recent git commits, project notes or .agents/PROJECT.md, and the conversation history or user message. The clearer the context, the fewer clarification questions it will ask.

When will Cipher ask questions instead of deciding?

It asks when multiple valid interpretations lead to significantly different outcomes, when critical context is missing, or when the action is high-risk or irreversible. For routine ambiguity it follows a safe default to avoid blocking flow.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
cipher skill by simota/agent-skills | VeilStrat