opencode-skills-collection 3.1.12 → 3.1.14

package/bundled-skills/hugo-to-markdown/scripts/inventory_hugo_rules.py

@@ -0,0 +1,188 @@
+#!/usr/bin/env python3
+
+import argparse
+import json
+import re
+from collections import Counter, defaultdict
+from pathlib import Path
+
+try:
+    import tomllib
+except ModuleNotFoundError:  # pragma: no cover
+    tomllib = None
+
+
+SHORTCODE_RE = re.compile(
+    r"\{\{[<%](?:/\*)?\s*(?!/)([A-Za-z0-9][A-Za-z0-9_/-]*)",
+    re.MULTILINE,
+)
+YAML_KEY_RE = re.compile(r"^([A-Za-z0-9_-]+):", re.MULTILINE)
+TOML_KEY_RE = re.compile(r"^([A-Za-z0-9_.-]+)\s*=", re.MULTILINE)
+
+
+def parse_args():
+    parser = argparse.ArgumentParser(
+        description="Inventory Hugo config, shortcodes, render hooks, and content patterns.",
+    )
+    parser.add_argument("--site-root", required=True, help="Path to the Hugo site root")
+    parser.add_argument("--output", help="Write JSON output to this file")
+    return parser.parse_args()
+
+
+def ensure_dir(path: Path) -> Path:
+    resolved = path.expanduser().resolve()
+    if not resolved.is_dir():
+        raise SystemExit(f"Site root does not exist or is not a directory: {resolved}")
+    return resolved
+
+
+def read_text(path: Path) -> str:
+    return path.read_text(encoding="utf-8", errors="replace")
+
+
+def relpath(path: Path, root: Path) -> str:
+    return str(path.resolve().relative_to(root))
+
+
+def find_config_files(root: Path):
+    direct = [
+        root / "hugo.toml",
+        root / "hugo.yaml",
+        root / "hugo.yml",
+        root / "hugo.json",
+        root / "config.toml",
+        root / "config.yaml",
+        root / "config.yml",
+        root / "config.json",
+    ]
+    found = [p for p in direct if p.is_file()]
+    config_dir = root / "config"
+    if config_dir.is_dir():
+        found.extend(sorted(p for p in config_dir.rglob("*") if p.is_file()))
+    return found
+
+
+def load_config_summary(path: Path):
+    suffix = path.suffix.lower()
+    if suffix == ".toml" and tomllib is not None:
+        data = tomllib.loads(read_text(path))
+    elif suffix == ".json":
+        data = json.loads(read_text(path))
+    else:
+        return {
+            "path": str(path),
+            "format": suffix.lstrip("."),
+            "parsed": False,
+        }
+
+    module_mounts = data.get("module", {}).get("mounts", [])
+    markup = data.get("markup", {})
+    goldmark = markup.get("goldmark", {})
+    passthrough = (
+        goldmark.get("extensions", {})
+        .get("passthrough", {})
+        .get("delimiters", {})
+    )
+    parser_attribute = goldmark.get("parser", {}).get("attribute", {})
+    render_hook_params = data.get("params", {}).get("render_hooks", {}).get("link", {})
+
+    return {
+        "path": str(path),
+        "format": suffix.lstrip("."),
+        "parsed": True,
+        "module_mounts": module_mounts,
+        "goldmark_passthrough_delimiters": passthrough,
+        "goldmark_block_attributes": parser_attribute.get("block"),
+        "link_render_error_level": render_hook_params.get("errorLevel"),
+    }
+
+
+def extract_frontmatter_keys(text: str):
+    if text.startswith("---\n"):
+        end = text.find("\n---", 4)
+        if end != -1:
+            return sorted(set(YAML_KEY_RE.findall(text[4:end])))
+    if text.startswith("+++\n"):
+        end = text.find("\n+++", 4)
+        if end != -1:
+            return sorted({k.split(".")[0] for k in TOML_KEY_RE.findall(text[4:end])})
+    return []
+
+
+def content_files(root: Path):
+    content_root = root / "content"
+    if not content_root.is_dir():
+        return []
+    exts = {".md", ".markdown", ".mdown", ".gotmpl"}
+    return sorted(p for p in content_root.rglob("*") if p.is_file() and p.suffix.lower() in exts)
+
+
+def main():
+    args = parse_args()
+    site_root = ensure_dir(Path(args.site_root))
+
+    shortcode_files = sorted((site_root / "layouts" / "_shortcodes").glob("*"))
+    render_hook_files = sorted((site_root / "layouts" / "_markup").glob("render-*"))
+
+    shortcode_usage = Counter()
+    shortcode_locations = defaultdict(list)
+    frontmatter_keys = Counter()
+    content_entries = []
+
+    for path in content_files(site_root):
+        text = read_text(path)
+        keys = extract_frontmatter_keys(text)
+        for key in keys:
+            frontmatter_keys[key] += 1
+
+        names = SHORTCODE_RE.findall(text)
+        unique_names = sorted(set(names))
+        for name in names:
+            shortcode_usage[name] += 1
+        for name in unique_names:
+            shortcode_locations[name].append(relpath(path, site_root))
+
+        content_entries.append(
+            {
+                "path": relpath(path, site_root),
+                "frontmatter_keys": keys,
+                "shortcodes": unique_names,
+            }
+        )
+
+    result = {
+        "site_root": str(site_root),
+        "config_files": [load_config_summary(path) for path in find_config_files(site_root)],
+        "shortcode_templates": [
+            {
+                "name": path.stem,
+                "path": relpath(path, site_root),
+            }
+            for path in shortcode_files
+            if path.is_file()
+        ],
+        "render_hooks": [
+            {
+                "name": path.stem,
+                "path": relpath(path, site_root),
+            }
+            for path in render_hook_files
+            if path.is_file()
+        ],
+        "frontmatter_key_frequency": dict(frontmatter_keys.most_common()),
+        "shortcode_usage_frequency": dict(shortcode_usage.most_common()),
+        "shortcode_locations": dict(sorted(shortcode_locations.items())),
+        "content_files": content_entries,
+    }
+
+    payload = json.dumps(result, indent=2, sort_keys=True)
+    if args.output:
+        output = Path(args.output)
+        output.parent.mkdir(parents=True, exist_ok=True)
+        output.write_text(payload + "\n", encoding="utf-8")
+    else:
+        print(payload)
+
+
+if __name__ == "__main__":
+    main()

package/bundled-skills/hyperexecute-skill/SKILL.md

@@ -0,0 +1,65 @@
+---
+name: hyperexecute-skill
+description: "Operates HyperExecute end-to-end for TestMu AI/LambdaTest cloud test execution: analyze projects, create YAML, validate locally, run CLI jobs, debug failures, and wire CI. Use when the user mentions HyperExecute, hyperexecute.yaml, HyperExecute CLI, autosplit, matrix execution,..."
+risk: unknown
+source: https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill
+source_repo: LambdaTest/agent-skills
+source_type: community
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/LambdaTest/agent-skills/blob/main/LICENSE
+---
+
+# HyperExecute Operator
+## When to Use
+
+Use this skill when you need operates HyperExecute end-to-end for TestMu AI/LambdaTest cloud test execution: analyze projects, create YAML, validate locally, run CLI jobs, debug failures, and wire CI. Use when the user mentions HyperExecute, hyperexecute.yaml, HyperExecute CLI, autosplit, matrix execution,...
+
+
+## Quick Start
+
+1. Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.
+2. Run `hyperexecute analyze` when the CLI is available; use local inspection only as fallback.
+3. Create or repair `hyperexecute.yaml` from the analyze output, project test commands, and templates in `reference/`.
+4. Run `node scripts/doctor.js --config hyperexecute.yaml` and `node scripts/validate-config.js hyperexecute.yaml`.
+5. Validate with the official CLI: `./hyperexecute --user "$LT_USERNAME" --key "$LT_ACCESS_KEY" --config hyperexecute.yaml --validate`.
+6. Ask before a real cloud job unless the user has explicitly opted into an autonomous HyperExecute session.
+7. For failures, download logs/artifacts/reports and use `reference/troubleshooting.md`.
+
+## Operating Rules
+
+- Treat the official HyperExecute CLI as the source of truth for analyze, validation, execution, logs, reports, and artifacts.
+- Use `LT_USERNAME` and `LT_ACCESS_KEY` from local environment variables or CI secrets; never hardcode credentials in YAML or docs.
+- Use `--job-secret-file` only for extra job-scoped secrets, preferably outside the repo or ignored by `.gitignore`/`.hyperexecuteignore`.
+- Prefer template-driven YAML over generator scripts because test commands, paths, and payload boundaries are project-specific.
+- Run safe local checks automatically; run real HyperExecute cloud jobs only after confirmation unless the user opted into autonomous mode.
+- In autonomous mode, validate first, run, inspect output, download logs/artifacts when useful, and retry only for actionable config/environment fixes.
+
+## Workflow
+
+- First run: analyze project, author YAML, run helper checks, run CLI validate, then request confirmation for the cloud job.
+- Debug: reproduce the failing CLI command, add `--verbose` when useful, download logs/artifacts/reports, fix one cause at a time.
+- CI: use CI secrets, add a validation stage before execution, set `CI=true` for quieter logs, and keep downloaded artifacts available for failed jobs.
+- Performance: tune `autosplit`, `concurrency`, cache keys, retries, smart ordering, and matrix/hybrid scope after one successful run.
+
+## Helper Scripts
+
+- `scripts/doctor.js`: checks CLI readiness, credentials, config presence, and optional official validation.
+- `scripts/validate-config.js`: lightweight config linting for common mistakes before official CLI validation.
+- `scripts/build-command.js`: prints safe validate/run/debug/download commands using environment variable references.
+- `scripts/summarize-artifacts.js`: summarizes downloaded logs, reports, and artifacts for triage.
+
+## References
+
+- CLI usage and flags: [reference/cli.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/cli.md)
+- YAML patterns: [reference/yaml-patterns.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/yaml-patterns.md)
+- Framework recipes: [reference/frameworks.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/frameworks.md)
+- CI/CD integration: [reference/ci-cd.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/ci-cd.md)
+- Security rules: [reference/security.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/security.md)
+- Troubleshooting: [reference/troubleshooting.md](https://github.com/LambdaTest/agent-skills/tree/main/hyperexecute-skill/reference/troubleshooting.md)
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream source and local project context.
+- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
+- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

package/bundled-skills/idea-refine/SKILL.md

@@ -0,0 +1,195 @@
+---
+name: idea-refine
+description: Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on...
+risk: unknown
+source: https://github.com/addyosmani/agent-skills/tree/main/skills/idea-refine
+source_repo: addyosmani/agent-skills
+source_type: community
+date_added: 2026-07-01
+license: MIT
+license_source: https://github.com/addyosmani/agent-skills/blob/main/LICENSE
+---
+
+# Idea Refine
+## When to Use
+
+Use this skill when you need refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on...
+
+
+Refines raw ideas into sharp, actionable concepts worth building through structured divergent and convergent thinking.
+
+## How It Works
+
+1.  **Understand & Expand (Divergent):** Restate the idea, ask sharpening questions, and generate variations.
+2.  **Evaluate & Converge:** Cluster ideas, stress-test them, and surface hidden assumptions.
+3.  **Sharpen & Ship:** Produce a concrete markdown one-pager moving work forward.
+
+## Usage
+
+This skill is primarily an interactive dialogue. Invoke it with an idea, and the agent will guide you through the process.
+
+```bash
+# Optional: Initialize the ideas directory
+bash skills/idea-refine/scripts/idea-refine.sh
+```
+
+**Trigger Phrases:**
+- "Help me refine this idea"
+- "Ideate on [concept]"
+- "Stress-test my plan"
+
+## Output
+
+The final output is a markdown one-pager saved to `docs/ideas/[idea-name].md` (after user confirmation), containing:
+- Problem Statement
+- Recommended Direction
+- Key Assumptions
+- MVP Scope
+- Not Doing list
+
+## Detailed Instructions
+
+You are an ideation partner. Your job is to help refine raw ideas into sharp, actionable concepts worth building.
+
+### Philosophy
+
+- Simplicity is the ultimate sophistication. Push toward the simplest version that still solves the real problem.
+- Start with the user experience, work backwards to technology.
+- Say no to 1,000 things. Focus beats breadth.
+- Challenge every assumption. "How it's usually done" is not a reason.
+- Show people the future — don't just give them better horses.
+- The parts you can't see should be as beautiful as the parts you can.
+
+### Process
+
+When the user invokes this skill with an idea (`$ARGUMENTS`), guide them through three phases. Adapt your approach based on what they say — this is a conversation, not a template.
+
+#### Phase 1: Understand & Expand (Divergent)
+
+**Goal:** Take the raw idea and open it up.
+
+1. **Restate the idea** as a crisp "How Might We" problem statement. This forces clarity on what's actually being solved.
+
+2. **Ask 3-5 sharpening questions** — no more. Focus on:
+   - Who is this for, specifically?
+   - What does success look like?
+   - What are the real constraints (time, tech, resources)?
+   - What's been tried before?
+   - Why now?
+
+   Use the `AskUserQuestion` tool to gather this input. Do NOT proceed until you understand who this is for and what success looks like.
+
+3. **Generate 5-8 idea variations** using these lenses:
+   - **Inversion:** "What if we did the opposite?"
+   - **Constraint removal:** "What if budget/time/tech weren't factors?"
+   - **Audience shift:** "What if this were for [different user]?"
+   - **Combination:** "What if we merged this with [adjacent idea]?"
+   - **Simplification:** "What's the version that's 10x simpler?"
+   - **10x version:** "What would this look like at massive scale?"
+   - **Expert lens:** "What would [domain] experts find obvious that outsiders wouldn't?"
+
+   Push beyond what the user initially asked for. Create products people don't know they need yet.
+
+**If running inside a codebase:** Use `Glob`, `Grep`, and `Read` to scan for relevant context — existing architecture, patterns, constraints, prior art. Ground your variations in what actually exists. Reference specific files and patterns when relevant.
+
+Read `frameworks.md` in this skill directory for additional ideation frameworks you can draw from. Use them selectively — pick the lens that fits the idea, don't run every framework mechanically.
+
+#### Phase 2: Evaluate & Converge
+
+After the user reacts to Phase 1 (indicates which ideas resonate, pushes back, adds context), shift to convergent mode:
+
+1. **Cluster** the ideas that resonated into 2-3 distinct directions. Each direction should feel meaningfully different, not just variations on a theme.
+
+2. **Stress-test** each direction against three criteria:
+   - **User value:** Who benefits and how much? Is this a painkiller or a vitamin?
+   - **Feasibility:** What's the technical and resource cost? What's the hardest part?
+   - **Differentiation:** What makes this genuinely different? Would someone switch from their current solution?
+
+   Read `refinement-criteria.md` in this skill directory for the full evaluation rubric.
+
+3. **Surface hidden assumptions.** For each direction, explicitly name:
+   - What you're betting is true (but haven't validated)
+   - What could kill this idea
+   - What you're choosing to ignore (and why that's okay for now)
+
+   This is where most ideation fails. Don't skip it.
+
+**Be honest, not supportive.** If an idea is weak, say so with kindness. A good ideation partner is not a yes-machine. Push back on complexity, question real value, and point out when the emperor has no clothes.
+
+#### Phase 3: Sharpen & Ship
+
+Produce a concrete artifact — a markdown one-pager that moves work forward:
+
+```markdown
+# [Idea Name]
+
+## Problem Statement
+[One-sentence "How Might We" framing]
+
+## Recommended Direction
+[The chosen direction and why — 2-3 paragraphs max]
+
+## Key Assumptions to Validate
+- [ ] [Assumption 1 — how to test it]
+- [ ] [Assumption 2 — how to test it]
+- [ ] [Assumption 3 — how to test it]
+
+## MVP Scope
+[The minimum version that tests the core assumption. What's in, what's out.]
+
+## Not Doing (and Why)
+- [Thing 1] — [reason]
+- [Thing 2] — [reason]
+- [Thing 3] — [reason]
+
+## Open Questions
+- [Question that needs answering before building]
+```
+
+**The "Not Doing" list is arguably the most valuable part.** Focus is about saying no to good ideas. Make the trade-offs explicit.
+
+Ask the user if they'd like to save this to `docs/ideas/[idea-name].md` (or a location of their choosing). Only save if they confirm.
+
+### Anti-patterns to Avoid
+
+- **Don't generate 20+ ideas.** Quality over quantity. 5-8 well-considered variations beat 20 shallow ones.
+- **Don't be a yes-machine.** Push back on weak ideas with specificity and kindness.
+- **Don't skip "who is this for."** Every good idea starts with a person and their problem.
+- **Don't produce a plan without surfacing assumptions.** Untested assumptions are the #1 killer of good ideas.
+- **Don't over-engineer the process.** Three phases, each doing one thing well. Resist adding steps.
+- **Don't just list ideas — tell a story.** Each variation should have a reason it exists, not just be a bullet point.
+- **Don't ignore the codebase.** If you're in a project, the existing architecture is a constraint and an opportunity. Use it.
+
+### Tone
+
+Direct, thoughtful, slightly provocative. You're a sharp thinking partner, not a facilitator reading from a script. Channel the energy of "that's interesting, but what if..." -- always pushing one step further without being exhausting.
+
+Read `examples.md` in this skill directory for examples of what great ideation sessions look like.
+
+## Red Flags
+
+- Generating 20+ shallow variations instead of 5-8 considered ones
+- Skipping the "who is this for" question
+- No assumptions surfaced before committing to a direction
+- Yes-machining weak ideas instead of pushing back with specificity
+- Producing a plan without a "Not Doing" list
+- Ignoring existing codebase constraints when ideating inside a project
+- Jumping straight to Phase 3 output without running Phases 1 and 2
+
+## Verification
+
+After completing an ideation session:
+
+- [ ] A clear "How Might We" problem statement exists
+- [ ] The target user and success criteria are defined
+- [ ] Multiple directions were explored, not just the first idea
+- [ ] Hidden assumptions are explicitly listed with validation strategies
+- [ ] A "Not Doing" list makes trade-offs explicit
+- [ ] The output is a concrete artifact (markdown one-pager), not just conversation
+- [ ] The user confirmed the final direction before any implementation work
+
+## Limitations
+
+- Use this skill only when the task clearly matches its upstream source and local project context.
+- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.
+- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.