skill-name

Name: skill-name
Author: hoodini

Other Community

Repo stars 211
Author repo ai-agents-skills

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Brief description of what this skill enables. Include trigger keywords that should activate this skill. Triggers on keyword1, ke…
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 “Quick Start”, “Core Patterns”, “Pattern 1”, “Pattern 2”, 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-name 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 “Quick Start / Core Patterns / Pattern 1” 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; 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.

Skill Title

One-line description of the skill's purpose.

Quick Start

// Minimal working example
// This should be copy-paste ready

Core Patterns

Pattern 1

// Implementation

Pattern 2

// Implementation

Common Use Cases

Use Case 1

// Example

Use Case 2

// Example

Resources

Official Docs: https://...
API Reference: See references/api.md

Fluxly profile Author and license come from source; runtime, permissions, and network are Fluxly detections or estimates

Fluxly category: Other
Author-declared agents: No explicit declaration found; this is not inferred or tested compatibility
Static check: 88 / 100 · heuristic scan, not runtime safety proof
Author / version / license: @hoodini · no license declared
Fluxly token estimate: Lean
Fluxly setup estimate: Plug-and-play
External API key: No requirement detected
Detected OS requirements: Unspecified
Runtime requirements: Unspecified
Detected file/system behavior: Read-only
Detected network behavior: Local-only
Install commands: None (reference only)

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-name-hoodini.preview

The current SKILL.md does not define a fixed output example.

SKILL.md SKILL.md

# Skill Title

One-line description of the skill's purpose.

## Quick Start

```typescript
// Minimal working example
// This should be copy-paste ready
```

## Core Patterns

### Pattern 1
```typescript
// Implementation
```

### Pattern 2
```typescript
// Implementation
```

## Common Use Cases

### Use Case 1
```typescript
// Example
```

### Use Case 2
```typescript
// Example
```

## Resources

- **Official Docs**: https://...
- **API Reference**: See `references/api.md`

Evidence boundary and execution chain

Author text anchors workflow facts; Fluxly only indexes current sections, terms, files, and commands.

sections -> Quick Start → Core Patterns → Pattern 1 → Pattern 2 → Common Use Cases → Use Case 1
terms    -> Official Docs · API Reference · One-line description of the skill's purpose. · - Official Docs: https://...
files/cmd -> references/api.md
body sha256 -> 1319aff1da12