fluxly Search skills… ⌘K 中文 Publish

new-agent

AI Community
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
AI
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
88 / 100 · community maintained
Author / version / license
@meyerdan · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Required · Vendor-specific
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No special requirements
Permissions
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
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 new-agent.preview 
---
name: new-agent
description: Generate a Camunda 8 agentic process with AI Agent connector and ad-hoc sub-process. Use when bu…
category: ai
runtime: no special runtime
---

# new-agent output preview

## PART A: Task fit
- Use case: Generate a Camunda 8 agentic process with AI Agent connector and ad-hoc sub-process. Use when building AI agent workflows with tool calling. Generate an agentic Camunda 8 BPMN process. Find and read the "Agentic BPMN" section of camunda-dev-guide.md for ad-hoc sub-process XML, connector task types, input targets, and fromAi() usage. requires Vendor-specif….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Decide Fit First / Design Intent / How To Use It” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Generate a Camunda 8 agentic process with AI Agent connector and ad-hoc sub-process. Use when building AI agent workflows with tool calling. Generate an agentic Camunda 8 BPMN process. Find and read the "Agentic BPMN" section of camunda-dev-guide.md for ad-hoc sub-process XML, connector task types, input targets, and fromAi() usage. requires Vendor-specif…”.
- **02** When the source has headings, the agent prioritizes “Decide Fit First / Design Intent / How To Use It” 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; may access external network resources; requires Vendor-specific API keys.

## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; requires Vendor-specific API keys.
- 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: Generate a Camunda 8 agentic process with AI Agent connector and ad-hoc sub-process. Use when building AI agent workflows with t…
  • 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 source has limited section structure, so treat it as an invocation rule: trigger, execution boundary, then validation.
  • 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 new-agent 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 “new-agent” before expanding.

Boundaries And Review

  • Dependencies: Prepare Vendor-specific API keys before running a full 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.