fluxly Search skills… ⌘K 中文 Publish

skill-verify

Other Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Other
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-verify.preview 
---
name: skill-verify
description: Evidence before claims — run verification commands before declaring work complete, fixed, or pas…
category: other
runtime: no special runtime
---

# skill-verify output preview

## PART A: Task fit
- Use case: Evidence before claims — run verification commands before declaring work complete, fixed, or passing NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE If you haven't run the verification command in this turn, you cannot claim it passes. Before claiming any success or expressing satisfaction: Skip any step = the claim is unverified. runs entirely lo….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “The Iron Law / The Gate / What Counts as Evidence” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Evidence before claims — run verification commands before declaring work complete, fixed, or passing NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE If you haven't run the verification command in this turn, you cannot claim it passes. Before claiming any success or expressing satisfaction: Skip any step = the claim is unverified. runs entirely lo…”.
- **02** When the source has headings, the agent prioritizes “The Iron Law / The Gate / What Counts as Evidence” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.
Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

  • Core job: Evidence before claims — run verification commands before declaring work complete, fixed, or passing NO COMPLETION CLAIMS WITHOU…
  • Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
  • Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

  • Structure: The skill is organized around “The Iron Law”, “The Gate”, “What Counts as Evidence”, “Red Flags — STOP and Verify”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
  • Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
  • Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

  • Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
  • Invocation: Name skill-verify directly; if the source includes slash commands, start with the command and then add task context.
  • Validation: Start small and check whether the result follows “The Iron Law / The Gate / What Counts as Evidence” before expanding.

Boundaries And Review

  • Dependencies: It usually needs no extra API key, so start with a small validation task.
  • Permissions: Declared permissions include read / write / shell-exec; ask the agent to state file, command, and rollback boundaries before acting.
  • Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.