fluxly Search skills… ⌘K 中文 Publish

skill-lint

Documentation Verified v1.4.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Documentation
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
93 / 100 · audit passed
Author / version / license
@cat-xierluo · v1.4.0 · MIT License - 详见 LICENSE.txt
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Env read
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，默认拥有全部工具权限。; 检出高风险片段：rm_rf_root

Output preview skill-lint.preview 
---
name: skill-lint
description: 对指定的 skill 进行格式合规性审查，生成结构化的审计报告。 使用 Glob 工具列出技能目录下的所有文件： ├── SKILL.md # 必需 ├── LICENSE.txt # 可选…
category: documentation
runtime: no special runtime
---

# skill-lint output preview

## PART A: Task fit
- Use case: 对指定的 skill 进行格式合规性审查，生成结构化的审计报告。 使用 Glob 工具列出技能目录下的所有文件： ├── SKILL.md # 必需 ├── LICENSE.txt # 可选 ├── CHANGELOG.md # 可选（推荐） runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “审查流程 / 1. 扫描目标技能 / 2. 检查目录结构” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “对指定的 skill 进行格式合规性审查，生成结构化的审计报告。 使用 Glob 工具列出技能目录下的所有文件： ├── SKILL.md # 必需 ├── LICENSE.txt # 可选 ├── CHANGELOG.md # 可选（推荐） runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “审查流程 / 1. 扫描目标技能 / 2. 检查目录结构” 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, read environment variables; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files, read environment variables; 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: 对指定的 skill 进行格式合规性审查，生成结构化的审计报告。 使用 Glob 工具列出技能目录下的所有文件： 检查项： [ ] SKILL.md 是否存在 [ ] 是否有不规范的目录（如 test/、docs/ 应改为 references/） [ ]…
  • 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 “审查流程”, “1. 扫描目标技能”, “2. 检查目录结构”, “3. 检查 Frontmatter”, 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-lint 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 “审查流程 / 1. 扫描目标技能 / 2. 检查目录结构” 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 / env-read; 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.