agentleFS
Sign inStart free
SKE-LabsSKE-Labs/agent-trading-skills/template/SKILL.md

skill-name

Skill17 starsChanged 4 months agoApache-2.0View on GitHub

What this skill does and when to use it. Use when [trigger condition 1], [trigger condition 2], or [trigger condition 3].

39 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-workflow and frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    NEVER: Critical mistake to avoid and why

    line 60

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill Title

Brief one-line introduction.

Identification

How to identify the pattern, setup, or condition:

  1. Step one — Description
  2. Step two — Description
  3. Step three — Description
ParameterValueNotes
Level 1X%Usage
Level 2Y%Usage

Workflow

1. Get Data

get_indicators(indicator_code="rsi", symbol=<symbol>, exchange=<exchange>, interval=<interval>, count=20)

2. Analyze

Describe what to look for in the data.

3. Mark on Chart

draw_chart_analysis(action="create", drawing={
    "type": "support",
    "points": [
        {"time": <timestamp>, "price": <price>},
        {"time": <timestamp>, "price": <price>}
    ],
    "options": {"text": "Label"}
})

4. Report to Orchestrator

Provide structured summary: setup, confidence, key levels (entry, stop, target), indicator values, risk flags.

Key Rules

  • Rule 1
  • Rule 2
  • NEVER: Critical mistake to avoid and why

Related Skills

  • skill-name — relationship note
  • skill-name — relationship note

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free