fluxly Search skills… ⌘K 中文 Publish

agentic-engineering

Documentation Community
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
88 / 100 · community maintained
Author / version / license
@affaan-m · no license declared
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
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 agentic-engineering.preview 
---
name: agentic-engineering
description: 在 AI 智能体执行大部分实施工作、而人类负责质量与风险控制的工程工作流中使用此技能。 当自动化格式化/代码检查工具已强制执行代码风格时，不要在仅涉及风格分歧的审查上浪费周期。 仅当较低层级的…
category: documentation
runtime: no special runtime
---

# agentic-engineering output preview

## PART A: Task fit
- Use case: 在 AI 智能体执行大部分实施工作、而人类负责质量与风险控制的工程工作流中使用此技能。 当自动化格式化/代码检查工具已强制执行代码风格时，不要在仅涉及风格分歧的审查上浪费周期。 仅当较低层级的模型失败且存在清晰的推理差距时，才升级模型层级。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “操作原则 / 评估优先循环 / 任务分解” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “在 AI 智能体执行大部分实施工作、而人类负责质量与风险控制的工程工作流中使用此技能。 当自动化格式化/代码检查工具已强制执行代码风格时，不要在仅涉及风格分歧的审查上浪费周期。 仅当较低层级的模型失败且存在清晰的推理差距时，才升级模型层级。 runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “操作原则 / 评估优先循环 / 任务分解” 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; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; 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: 在 AI 智能体执行大部分实施工作、而人类负责质量与风险控制的工程工作流中使用此技能。 1. 在执行前定义完成标准。 2. 将工作分解为智能体可处理的单元。 3. 根据任务复杂度路由模型层级。 4. 使用评估和回归检查进行度量。 1. 定义能力评估和回归评…
  • 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 “操作原则”, “评估优先循环”, “任务分解”, “模型路由”, 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 agentic-engineering 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 “操作原则 / 评估优先循环 / 任务分解” 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; 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.