fluxly Search skills… ⌘K 中文 Publish

ceo-setup

Engineering Verified v0.4.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Engineering
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
92 / 100 · audit passed
Author / version / license
@nearai · v0.4.0 · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
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 ceo-setup.preview 
---
name: ceo-setup
description: One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting pr…
category: engineering
runtime: no special runtime
---

# ceo-setup output preview

## PART A: Task fit
- Use case: One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a `commitments` project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Order of operations (sequential, one tool call at a time) / Step 1: Declare the project / Step 2: Write context” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a `commitments` project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.”.
- **02** When the source has headings, the agent prioritizes “Order of operations (sequential, one tool call at a time) / Step 1: Declare the project / Step 2: Write context” 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; usually needs no extra API key.

## Running Rules
- read files, write/modify files, run shell commands; may access external network resources; 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: One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning an…
  • 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 “Order of operations (sequential, one tool call at a time)”, “Step 1: Declare the project”, “Step 2: Write context”, “Step 3: Schema and calibration”, 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 ceo-setup 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 “Order of operations (sequential, one tool call at a time) / Step 1: Declare the project / Step 2: Write context” 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.