trader-hand-skill

Data Verified v1.0.0
Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network
Domain
Data · trading · finance · stocks
Compatible agents
  • Claude Code
  • Cursor
  • Cline
  • Codex
  • Windsurf
  • Gemini CLI
  • +20
Trust score
98 / 100 · audit passed
Author / version / license
@RightNow-AI · v1.0.0 · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Required · Vendor-specific
Operating systems
macOS · Linux · Windows · WSL
Runtime requirements
Python
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.

Output preview trader-hand-skill.preview
---
name: trader-hand-skill
description: Expert knowledge for autonomous market intelligence and trading — technical analysis, risk manag…
category: data
runtime: Python
---

# trader-hand-skill output preview

## PART A: Task fit
- Use case: Expert knowledge for autonomous market intelligence and trading — technical analysis, risk management, Alpaca API, financial data sources Formula: RSI = 100 - (100 / (1 + RS)) Where: RS = Average Gain / Average Loss over N periods (default N = 14) Step-by-step calculation: Worked example (14-period): Avg Gain over 14 periods = 1.02 requires Vendor-specifi….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Reference Knowledge / 1. Technical Analysis Indicators Reference / RSI (Relative Strength Index)” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Expert knowledge for autonomous market intelligence and trading — technical analysis, risk management, Alpaca API, financial data sources Formula: RSI = 100 - (100 / (1 + RS)) Where: RS = Average Gain / Average Loss over N periods (default N = 14) Step-by-step calculation: Worked example (14-period): Avg Gain over 14 periods = 1.02 requires Vendor-specifi…”.
- **02** When the source has headings, the agent prioritizes “Reference Knowledge / 1. Technical Analysis Indicators Reference / RSI (Relative Strength Index)” 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: Expert knowledge for autonomous market intelligence and trading — technical analysis, risk management, Alpaca API, financial dat…
  • 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 “Reference Knowledge”, “1. Technical Analysis Indicators Reference”, “RSI (Relative Strength Index)”, “MACD (Moving Average Convergence Divergence)”, 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 trader-hand-skill 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 “Reference Knowledge / 1. Technical Analysis Indicators Reference / RSI (Relative Strength Index)” 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.