@hyperflow.fun/ghost 0.0.1

package/dist/skills/builtin/skill-creator/scripts/quick_validate.py

@@ -0,0 +1,213 @@
+#!/usr/bin/env python3
+"""
+Minimal validator for Ghost skill folders.
+"""
+
+import re
+import sys
+from pathlib import Path
+from typing import Optional
+
+try:
+    import yaml
+except ModuleNotFoundError:
+    yaml = None
+
+MAX_SKILL_NAME_LENGTH = 64
+ALLOWED_FRONTMATTER_KEYS = {
+    "name",
+    "description",
+    "metadata",
+    "always",
+    "license",
+    "allowed-tools",
+}
+ALLOWED_RESOURCE_DIRS = {"scripts", "references", "assets"}
+PLACEHOLDER_MARKERS = ("[todo", "todo:")
+
+
+def _extract_frontmatter(content: str) -> Optional[str]:
+    lines = content.splitlines()
+    if not lines or lines[0].strip() != "---":
+        return None
+    for i in range(1, len(lines)):
+        if lines[i].strip() == "---":
+            return "\n".join(lines[1:i])
+    return None
+
+
+def _parse_simple_frontmatter(frontmatter_text: str) -> Optional[dict[str, str]]:
+    """Fallback parser for simple frontmatter when PyYAML is unavailable."""
+    parsed: dict[str, str] = {}
+    current_key: Optional[str] = None
+    multiline_key: Optional[str] = None
+
+    for raw_line in frontmatter_text.splitlines():
+        stripped = raw_line.strip()
+        if not stripped or stripped.startswith("#"):
+            continue
+
+        is_indented = raw_line[:1].isspace()
+        if is_indented:
+            if current_key is None:
+                return None
+            current_value = parsed[current_key]
+            parsed[current_key] = f"{current_value}\n{stripped}" if current_value else stripped
+            continue
+
+        if ":" not in stripped:
+            return None
+
+        key, value = stripped.split(":", 1)
+        key = key.strip()
+        value = value.strip()
+        if not key:
+            return None
+
+        if value in {"|", ">"}:
+            parsed[key] = ""
+            current_key = key
+            multiline_key = key
+            continue
+
+        if (value.startswith('"') and value.endswith('"')) or (
+            value.startswith("'") and value.endswith("'")
+        ):
+            value = value[1:-1]
+        parsed[key] = value
+        current_key = key
+        multiline_key = None
+
+    if multiline_key is not None and multiline_key not in parsed:
+        return None
+    return parsed
+
+
+def _load_frontmatter(frontmatter_text: str) -> tuple[Optional[dict], Optional[str]]:
+    if yaml is not None:
+        try:
+            frontmatter = yaml.safe_load(frontmatter_text)
+        except yaml.YAMLError as exc:
+            return None, f"Invalid YAML in frontmatter: {exc}"
+        if not isinstance(frontmatter, dict):
+            return None, "Frontmatter must be a YAML dictionary"
+        return frontmatter, None
+
+    frontmatter = _parse_simple_frontmatter(frontmatter_text)
+    if frontmatter is None:
+        return None, "Invalid YAML in frontmatter: unsupported syntax without PyYAML installed"
+    return frontmatter, None
+
+
+def _validate_skill_name(name: str, folder_name: str) -> Optional[str]:
+    if not re.fullmatch(r"[a-z0-9]+(?:-[a-z0-9]+)*", name):
+        return (
+            f"Name '{name}' should be hyphen-case "
+            "(lowercase letters, digits, and single hyphens only)"
+        )
+    if len(name) > MAX_SKILL_NAME_LENGTH:
+        return (
+            f"Name is too long ({len(name)} characters). "
+            f"Maximum is {MAX_SKILL_NAME_LENGTH} characters."
+        )
+    if name != folder_name:
+        return f"Skill name '{name}' must match directory name '{folder_name}'"
+    return None
+
+
+def _validate_description(description: str) -> Optional[str]:
+    trimmed = description.strip()
+    if not trimmed:
+        return "Description cannot be empty"
+    lowered = trimmed.lower()
+    if any(marker in lowered for marker in PLACEHOLDER_MARKERS):
+        return "Description still contains TODO placeholder text"
+    if "<" in trimmed or ">" in trimmed:
+        return "Description cannot contain angle brackets (< or >)"
+    if len(trimmed) > 1024:
+        return f"Description is too long ({len(trimmed)} characters). Maximum is 1024 characters."
+    return None
+
+
+def validate_skill(skill_path):
+    """Validate a skill folder structure and required frontmatter."""
+    skill_path = Path(skill_path).resolve()
+
+    if not skill_path.exists():
+        return False, f"Skill folder not found: {skill_path}"
+    if not skill_path.is_dir():
+        return False, f"Path is not a directory: {skill_path}"
+
+    skill_md = skill_path / "SKILL.md"
+    if not skill_md.exists():
+        return False, "SKILL.md not found"
+
+    try:
+        content = skill_md.read_text(encoding="utf-8")
+    except OSError as exc:
+        return False, f"Could not read SKILL.md: {exc}"
+
+    frontmatter_text = _extract_frontmatter(content)
+    if frontmatter_text is None:
+        return False, "Invalid frontmatter format"
+
+    frontmatter, error = _load_frontmatter(frontmatter_text)
+    if error:
+        return False, error
+
+    unexpected_keys = sorted(set(frontmatter.keys()) - ALLOWED_FRONTMATTER_KEYS)
+    if unexpected_keys:
+        allowed = ", ".join(sorted(ALLOWED_FRONTMATTER_KEYS))
+        unexpected = ", ".join(unexpected_keys)
+        return (
+            False,
+            f"Unexpected key(s) in SKILL.md frontmatter: {unexpected}. Allowed properties are: {allowed}",
+        )
+
+    if "name" not in frontmatter:
+        return False, "Missing 'name' in frontmatter"
+    if "description" not in frontmatter:
+        return False, "Missing 'description' in frontmatter"
+
+    name = frontmatter["name"]
+    if not isinstance(name, str):
+        return False, f"Name must be a string, got {type(name).__name__}"
+    name_error = _validate_skill_name(name.strip(), skill_path.name)
+    if name_error:
+        return False, name_error
+
+    description = frontmatter["description"]
+    if not isinstance(description, str):
+        return False, f"Description must be a string, got {type(description).__name__}"
+    description_error = _validate_description(description)
+    if description_error:
+        return False, description_error
+
+    always = frontmatter.get("always")
+    if always is not None and not isinstance(always, bool):
+        return False, f"'always' must be a boolean, got {type(always).__name__}"
+
+    for child in skill_path.iterdir():
+        if child.name == "SKILL.md":
+            continue
+        if child.is_dir() and child.name in ALLOWED_RESOURCE_DIRS:
+            continue
+        if child.is_symlink():
+            continue
+        return (
+            False,
+            f"Unexpected file or directory in skill root: {child.name}. "
+            "Only SKILL.md, scripts/, references/, and assets/ are allowed.",
+        )
+
+    return True, "Skill is valid!"
+
+
+if __name__ == "__main__":
+    if len(sys.argv) != 2:
+        print("Usage: python quick_validate.py <skill_directory>")
+        sys.exit(1)
+
+    valid, message = validate_skill(sys.argv[1])
+    print(message)
+    sys.exit(0 if valid else 1)

package/dist/skills/builtin/skills-sh/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: skills-sh
+description: "Search and install agent skills from skills.sh, the open skill directory. Triggers: find a skill, search skills, install skill, skills.sh, skill directory"
+metadata: {"ghost":{"emoji":"🔮","requires":{"bins":["npx"]}}}
+---
+
+# skills.sh
+
+Open skill directory for AI agents (91,000+ skills). Search by keyword.
+
+## When to use
+
+Use this skill when the user asks any of:
+- "find a skill on skills.sh"
+- "search skills.sh"
+- "install a skill from skills.sh"
+- "what skills are on skills.sh?"
+
+## Search
+
+```bash
+npx --yes skills find react
+```
+
+## Install
+
+**Step 1:** Install the skill globally:
+```bash
+npx --yes skills add <owner/repo@skill-name> -g -y --copy
+```
+
+**Step 2:** Move to Ghost workspace. The CLI installs to `$HOME/.agents/skills/` or `$HOME/.claude/skills/` depending on the detected agent. Check which one has the skill, then move:
+```bash
+mv $HOME/.agents/skills/<skill-name> $HOME/.ghost/workspace/skills/ 2>/dev/null || mv $HOME/.claude/skills/<skill-name> $HOME/.ghost/workspace/skills/
+```
+
+Replace `<owner/repo@skill-name>` with the source from search results. Replace `<skill-name>` with the installed directory name.
+
+## List installed (skills.sh registry)
+
+```bash
+npx --yes skills list -g
+```
+
+## Update
+
+```bash
+npx --yes skills update
+```
+
+## Notes
+
+- Requires Node.js (`npx` comes with it).
+- No API key needed for search and install.
+- Always use `-g --copy` flags to install globally with real files (not symlinks).
+- The CLI may install to `$HOME/.agents/skills/` or `$HOME/.claude/skills/` — always check both and move to `$HOME/.ghost/workspace/skills/`.

package/dist/skills/builtin/technical-analysis/SKILL.md

@@ -0,0 +1,242 @@
+---
+name: technical-analysis
+description: "Technical chart analysis — read indicators and levels, then share your view. Triggers: technical analysis, chart analysis, EMA, RSI, MACD, support, resistance, trend, levels, key levels, Ichimoku, Bollinger, Fibonacci, pivot, squeeze, ADX, ATR."
+---
+
+# Technical Analysis
+
+Read the chart and tell the trader what you see — with a clear view, not a data dump.
+
+## When to Activate
+
+- "How does BTC look technically?"
+- "Technical analysis on ETH"
+- "Where's BTC support/resistance?"
+- "Is BTC trending or sideways?"
+
+## Gather Data
+
+Call in parallel:
+
+```
+ghost_get_indicators(symbol, interval)   → trend, momentum, volatility, volume
+ghost_get_levels(symbol, interval)       → S/R levels
+ghost_get_price(symbol)                  → current price
+```
+
+Default: 4h for structure. Add 1h if trader asks about short-term. Add 1d for big picture.
+
+## How to Analyze
+
+**Step 1 — Form your view:** Look at all the data. What's the overall picture? Trending up, down, or sideways? Where is price relative to key levels? Any extreme signals?
+
+**Step 2 — Pick what matters:** From 15 indicators and multiple levels, select the 3-5 data points that tell the story. Skip everything else.
+
+**Step 3 — State your view clearly:** Lead with your conclusion. Then show the supporting data.
+
+## How to Communicate
+
+**Lead with the view, support with data.** Don't list all indicators. Don't categorize levels as "Psychological", "Minor", "Immediate" — just say what matters.
+
+**Keep it scannable — one idea per paragraph.** Don't chain 4 indicators into one dense block. Break after your view, after indicator data, after levels, and after your recommendation. Each paragraph should be 1-3 sentences max. Short paragraphs with whitespace between them are far easier to scan than a wall of text.
+
+Good (note: indicator names wrapped in `<ind>`, price levels wrapped in `<lvl>` — see Indicator Mentions and Level Mentions sections):
+
+```
+BTC is in a 4h downtrend — price below <ind name="ema">EMA50 and EMA200</ind>. <ind name="adx">ADX 32</ind> shows decent trend strength.
+
+Nearest support at <lvl price="65000">$65,000</lvl> has been tested 3 times. If <lvl price="65000">$65k</lvl> breaks, next zone is $63,000-$64,000. Resistance above at <lvl price="68500">$68,500</lvl>.
+
+<chart symbol="BTC" interval="4h" indicators="adx" levels="65000,68500" />
+```
+
+```
+ETH has been sideways for 3 days, <ind name="bb">Bollinger Bands</ind> are squeezing — a big move is building. <ind name="rsi">RSI 48</ind>, neutral.
+
+Wait for a clear breakout direction before entering.
+
+<chart symbol="ETH" interval="4h" indicators="bb,rsi" />
+```
+
+```
+SOL is retesting the daily <ind name="ema">EMA200</ind> at <lvl price="180">$180</lvl>. <ind name="rsi">RSI 35</ind>, near oversold.
+
+If it holds the <ind name="ema">EMA200</ind>, this could be a decent entry point toward <lvl price="195">$195</lvl>.
+
+<chart symbol="SOL" interval="1d" indicators="rsi" levels="180,195" />
+```
+
+Bad:
+- Tables listing every S/R level with categories (Psychological, Minor, Major, Immediate, Key)
+- Listing all 15 indicators in a report format
+- "Bullish Score: 7/10"
+- "TECHNICAL ANALYSIS REPORT"
+- Dumping raw numbers without a conclusion
+
+## S/R Levels
+
+**Don't list all levels.** Pick the 1-2 most relevant:
+- The nearest strong support below (for longs: where to SL)
+- The nearest strong resistance above (for longs: target / for shorts: where to SL)
+- Mention price distance naturally: "$65,000 support is 2.5% below"
+
+## Boundaries
+
+- Have a view, but don't say "buy" or "sell". Say "bullish setup", "risky entry here", "could be a good entry".
+- Don't predict exact moves. "RSI oversold, could bounce" — not "will bounce to $70k".
+- Insufficient data (< 30 candles): say so.
+
+## Chart Visualization
+
+`<chart>` tags render as a clickable pill inside the message bubble
+(e.g. "BTC · 4h →"). Clicking the pill opens the full interactive
+chart as a fullscreen overlay — that's the reading surface.
+
+**This means**: the pill IS the render. It is always visible when the
+tag is well-formed. If a trader ever says "the chart isn't showing" or
+"can't see it", DO NOT apologise or blame a "frontend issue" — tell
+them to click the pill to open the fullscreen view. The pill is how
+charts have always rendered; there's no inline chart.
+
+### Chart emission
+
+Every TA response MUST end with one `<chart ... />` self-closing tag on the very last line. No text after the tag.
+
+**You MUST write at least one sentence of prose before the tag — a bare-pill response (chart tag with no text) reads as the assistant refusing to answer.** If the user only says "show chart BTC 4h" and you have nothing analytical to add, still write one short framing line before the tag (e.g. "BTC 4h — latest candles with EMAs and levels marked."). Never ship a response whose only visible content is the pill.
+
+Every `<ind name="X">` you write MUST appear in the chart's `indicators="..."`. Every `<lvl price="Y">` MUST appear in `levels="..."`. Before sending, if the last line isn't `<chart .../>` and you wrote any `<ind>` or `<lvl>`, stop and add it.
+
+This emission rule is the master contract — other skills (position-monitor, pre-trade-advisory, risk-manager, briefing) point back here.
+
+### When to Include
+
+- Full technical analysis → YES (one chart is enough)
+- Quick price check → NO
+- Discussing specific patterns, levels, setups → YES
+- Simple trend answer → NO
+
+### How to Emit
+
+**ALWAYS place chart tags at the very end of your response — after ALL text.** Never put text after chart tags.
+
+Your analysis text here...
+
+<chart symbol="ETH" interval="4h" indicators="rsi"
+       levels="2400,2650"
+       focus-time="2026-04-01,2026-04-11"
+       focus-price="2350,2700" />
+
+### Attributes
+
+- symbol (required): the asset
+- interval: match timeframe you're discussing. Default 4h.
+- indicators: which extras to fetch alongside base EMAs. Include every
+  indicator you reference in text so `<ind>` mentions have data to hover/click.
+  Main pane overlays: bb, ichimoku, keltner, vwap.
+  Sub-pane indicators: rsi, macd, adx, stochrsi, obv, williamsr, cci, atr.
+  No per-chart limit — the pill shows the count, and fullscreen-on-click
+  renders all indicators.
+- levels: the 1-3 key S/R prices you highlight in text. Do NOT list every level — pick only the ones central to your thesis.
+- focus-time: start,end dates — frame the time period of the pattern.
+- focus-price: low,high prices — frame the price zone around key levels.
+
+### Rules — KEEP CHARTS CLEAN
+
+- **Default chart = candles + EMAs + levels.** No extra indicators unless you discuss them.
+- **ONE sub-pane indicator per chart.** Never combine rsi + macd + adx in one tag. If you discuss RSI divergence AND MACD crossover, use two separate chart tags.
+- **ONE overlay per chart.** Don't stack bb + ichimoku + keltner.
+- **Max 3 levels.** Pick the 1-3 S/R levels most relevant to your thesis. The backend already filters, but don't overload the `levels` attribute either.
+- **Split by story, not by indicator count.** One chart showing the main setup is usually enough. Only add a second chart when you explicitly discuss a different indicator.
+- Only include indicators you discuss in text.
+- focus frames the story — zoom to where the action is.
+
+## Indicator Mentions (`<ind>`) — MANDATORY
+
+**Every** indicator name you write in TA prose MUST be wrapped in `<ind name="...">` tags. **Every** indicator you wrap MUST also appear in your `<chart indicators="...">` attribute (so the data is fetched). The web UI renders each mention as a hoverable + clickable chart preview. Skipping a wrap or leaving an indicator out of the chart attribute = the trader loses the preview = defect.
+
+Treat this as a strict output contract: count the indicator names in your draft prose, then count `<ind>` tags — they must match.
+
+### Allowed names (strict whitelist)
+
+`ema`, `bb`, `ichimoku`, `keltner`, `vwap` (overlays), `rsi`, `macd`, `adx`, `stochrsi`, `obv`, `williamsr`, `cci`, `atr` (sub-panes)
+
+### Rules
+
+- MANDATORY: every indicator name in prose MUST be wrapped — no exceptions, even brief mentions ("OBV is falling" → `<ind name="obv">OBV</ind> is falling`). This includes section labels and bullet starts: "Ichimoku: price above cloud" → `<ind name="ichimoku">Ichimoku</ind>: price above cloud`. "MACD histogram positive" → `<ind name="macd">MACD</ind> histogram positive`.
+- MANDATORY: every wrapped indicator MUST be in your `<chart indicators="...">` attribute. If you mention 7 indicators, your chart attribute lists all 7.
+- Wrap the shortest meaningful phrase (e.g. `<ind name="rsi">RSI 48</ind>`, not `<ind name="rsi">RSI 48 is neutral</ind>`).
+- Use `<ind>` inline within prose — never on its own line.
+- One `<ind>` per indicator mention. Don't nest tags.
+- `<ind name="ema">` groups all EMAs (21/50/200) — no per-period tags. "All four EMAs", "EMA 50", "EMAs stacked bullish" all use `name="ema"`.
+- If no `<chart>` tag in the message, don't use `<ind>` — they need chart data.
+
+### Good — every indicator wrapped, all listed in chart
+
+```
+LINK is decisively weak — below all four <ind name="ema">EMAs</ind> with the bearish stack, below <ind name="ichimoku">Ichimoku cloud</ind>, and <ind name="vwap">VWAP</ind> overhead at <price>$9.06</price>.
+
+Oscillators are oversold: <ind name="stochrsi">StochRSI</ind> 9.5/9.9, <ind name="williamsr">Williams %R</ind> -94.4, <ind name="cci">CCI</ind> -97.7. <ind name="rsi">RSI</ind> 41.9 also low.
+
+<ind name="adx">ADX</ind> 13.7 — no trend. <ind name="obv">OBV</ind> falling confirms the weakness.
+
+<chart symbol="LINK" interval="4h" indicators="ema,ichimoku,vwap,stochrsi,williamsr,cci,rsi,adx,obv" levels="8.72,9.06" />
+```
+
+Count check: 9 indicator names in prose ↔ 9 `<ind>` tags ↔ 9 names in `indicators=`.
+
+### Bad
+
+```
+<!-- Don't mention an indicator without wrapping (loses preview) -->
+RSI 38 is neutral-bearish.
+<chart symbol="BTC" interval="4h" indicators="rsi" />
+
+<!-- Don't use <ind> for indicators not in chart's indicators= attribute -->
+<ind name="ichimoku">Ichimoku</ind> looks bearish.
+<chart symbol="BTC" interval="4h" indicators="rsi" />
+
+<!-- Don't use unknown names -->
+<ind name="fibonacci">Fibonacci</ind>
+
+<!-- Don't use <ind> without a <chart> tag -->
+<ind name="rsi">RSI</ind> is at 70.
+```
+
+## Level Mentions (`<lvl>`)
+
+**ALWAYS wrap price levels in `<lvl price="...">` tags** when you mention a price that appears in your `<chart levels="...">` attribute. The web UI renders a hoverable mini-chart with a highlighted horizontal line at that price. Supports/resistance detected in the backend get colored automatically (green/red); other prices show as neutral.
+
+### Rules
+
+- Wrap the visible price text (e.g. `<lvl price="65000">$65,000</lvl>`) — the `price` attribute must be the raw number without `$`, commas, or suffixes.
+- Only wrap levels that are in your `<chart levels="...">` list — if not in the chart, leave as plain text.
+- Use for: support, resistance, Fibonacci retracements, pivot points, swing highs/lows — any price-level discussion.
+- You may wrap the SAME price multiple times in the same response (every mention is independent).
+- Accept formats inside the tag: `$65,000`, `$65k`, `65,000`, `65000` — all fine as display text. The `price` attribute stays `65000`.
+
+### Good
+
+```
+Support at <lvl price="65000">$65,000</lvl> has held 3 times. Break below opens up <lvl price="62500">$62,500</lvl>.
+
+<chart symbol="BTC" interval="4h" indicators="adx" levels="65000,62500,68500" />
+```
+
+### Bad
+
+```
+<!-- Don't wrap prices that aren't in the chart's levels attribute -->
+Support at <lvl price="65000">$65,000</lvl>.
+<chart symbol="BTC" interval="4h" levels="68500" />
+
+<!-- Don't include formatting in the price attribute -->
+<lvl price="$65,000">$65,000</lvl>   (wrong — use price="65000")
+```
+
+## Tools
+
+```
+ghost_get_indicators(symbol, interval?, indicators?)
+ghost_get_levels(symbol, interval?, lookback?, method?)
+ghost_get_price(symbol)
+```