bytelandtechnology
- 47 skills
- 0 followers
- 17 hours ago last updated
- ▌ Acp Agent CLI · bytelandtechnology bundleFull-function ACP CLI for developers and automation, exposing the complete ACP protocol surface and an integrated agent registry for discovering, managing, and installing ACP agents through one unified command-line workflow.
- ▌ Dota Agent CLI · bytelandtechnology bundleLive provider-backed Dota 2 knowledge and live-match CLI for agent-friendly hero, item, match state, and source lookups
- ▌ Jellyfin Agent CLI · bytelandtechnology bundleTerminal client for Jellyfin media servers — browse libraries, control playback, manage users, run admin tasks, and automate workflows from the command line. Use this skill whenever the user mentions Jellyfin, media servers, streaming, home theater automation, or asks to interact with a Jellyfin instance programmatically. Also use when the user is working in this repository (jellyfin-agent-cli) — building, testing, debugging, or extending the CLI itself. Triggers on: "jellyfin", "media server", "jellyfin cli", "jellyfin-agent-cli", "streaming automation", "home theater cli", "jellyfin e2e", "jellyfin api", "browse my movies", "play media from terminal".
- ▌
- ▌ Telegram Agent CLI · bytelandtechnology bundleTelegram automation CLI with structured output, runtime-state inspection, interactive REPL, scenario testing, and MCP server for AI agents
- ▌ Gemini Prompting · bytelandtechnology bundleInternal guidance for composing Gemini prompts for coding, review, diagnosis, and research tasks inside the Gemini Claude Code plugin
- ▌ Gemini CLI Runtime · bytelandtechnologyInternal helper contract for calling the Gemini-backed gemini-companion runtime from Claude Code
- ▌ Gemini Result Handling · bytelandtechnologyInternal guidance for presenting Gemini helper output back to the user
- ▌ Rust CLI · bytelandtechnology bundleUmbrella guide for the rust-cli skill family: route Rust CLI Skill work through intake, description, scaffolding, feature extension, validation, and publish/release while preserving the constitution, package layout contract, and packaging boundaries.
- ▌ Rust CLI Extend · bytelandtechnologyExtension stage for the rust-cli skill family: add the supported stream or repl feature to an existing scaffolded project while preserving the shared runtime contract.
- ▌ Rust CLI Intake · bytelandtechnologyTriage stage for the rust-cli skill family: classify the request as description, scaffold, extend, validate, or publish, confirm required inputs, load the shared rules, and hand off to the correct next phase.
- ▌ Rust CLI Publish · bytelandtechnologyPublish stage for the rust-cli skill family: close the workflow with repository-owned packaging and release actions, including report-only summaries, dry runs, exact-mirror rehearsals, destination configuration checks, and the supported GitHub Actions publication path.
- ▌ Rust CLI Scaffold · bytelandtechnologyScaffold stage for the rust-cli skill family: create a new Rust CLI Skill project from the package templates and prepare it for validation.
- ▌ Rust CLI Validate · bytelandtechnologyValidation stage for the rust-cli skill family: run the documented compliance checks for an existing project and report whether it is constitution-compliant, usable with warnings, or blocked by errors.
- ▌ Rust CLI Description · bytelandtechnologyDescription stage for the rust-cli skill family: define or refresh the generated skill description contract before downstream stages change scaffold, feature, validation, or packaging surfaces.
- ▌ CLI Forge · bytelandtechnology bundleRouter for the cli-forge skill family: classify the request, detect missing contract baselines, check filesystem state, and route to the earliest incomplete or takeover stage.
- ▌ CLI Forge Plan · bytelandtechnology bundlePlan stage for the cli-forge skill family: define the detailed CLI contract including commands, flags, output formats, stream/repl/daemon capability scope, the daemon app-server contract, and runtime behavior before scaffold or extend stages proceed.
- ▌ CLI Forge Design · bytelandtechnology bundleDesign stage for the cli-forge skill family: define or refresh the generated skill's high-level identity, purpose, positioning, and description contract before downstream stages proceed.
- ▌ CLI Forge Extend · bytelandtechnology bundleExtend stage for the cli-forge skill family: add stream or repl features to an existing scaffolded skill project or to a takeover-adopted project that already matches the scaffold-compatible layout.
- ▌ CLI Forge Publish · bytelandtechnology bundlePublish stage for the cli-forge skill family: manage the GitHub Release and multi-package npm publication automation for a generated skill.
- ▌ CLI Forge Scaffold · bytelandtechnology bundleScaffold stage for the cli-forge skill family: create a new Rust CLI Skill project from the authoritative templates and prepare it for validation.
- ▌ CLI Forge Takeover · bytelandtechnology bundleRecovery stage for the cli-forge skill family: adopt an existing Rust CLI Skill project that lacks cli-forge contracts by reconstructing design/plan artifacts from the current implementation, enforcing gates, and stopping for user decisions on ambiguity.
- ▌ CLI Forge Validate · bytelandtechnology bundleValidate stage for the cli-forge skill family: run the 47-check compliance ruleset against a scaffolded, takeover-adopted, or extended skill project and compare any daemon surface against the declared CLI plan.
- ▌ Ghidra Headless · bytelandtechnology bundleUmbrella guide for the standalone Ghidra headless skill family: route to the right phase skill, preserve headless-only constraints, and audit speckit planning without downstream hooks.
- ▌ Ghidra Headless Intake · bytelandtechnology bundlePhase skill for target intake and project initialization before speckit planning or audit.
- ▌ Ghidra Headless Evidence · bytelandtechnology bundlePhase skill for evidence extraction, replay expectations, and audit of generated planning artifacts.
- ▌ Ghidra Headless Script Review · bytelandtechnology bundlePhase skill for reusable headless Ghidra script authoring, review, registration, and contract-based audit.
- ▌ Ghidra Headless Auto Evolution · bytelandtechnology bundleExplicit child skill for extracting reusable improvements from real Ghidra work, resolving overlap, and promoting tracked assets when one task provides complete evidence.
- ▌ Ghidra Headless Frida Evidence · bytelandtechnology bundlePhase skill for import-only Frida dynamic evidence normalization, replay expectations, and audit of generated planning artifacts.
- ▌ Ghidra Headless Frida Runtime Injection · bytelandtechnology bundlePhase skill for reproducible CLI/headless Frida runtime capture, reusable common script selection, and capture-manifest handoff into evidence import.
- ▌ Ghidra Headless Progressive Decompilation · bytelandtechnology bundlePhase skill for Stage 6 selected decompilation, incremental compare, and audit of generated planning artifacts.
- ▌ Headless Ghidra · bytelandtechnology bundleEntry skill for the Headless Ghidra YAML-first reverse-engineering pipeline. Use when the user asks to analyze, decompile, triage, resume, or iterate on a binary target with Ghidra/headless-ghidra. Reads artifacts/<target>/pipeline-state.yaml, routes P0–P4 phase skills, runs gate checks, and manages review pauses. Performs zero analysis work itself.
- ▌ Ghidra Agent CLI · bytelandtechnology bundleRust CLI reference for the headless-ghidra pipeline. Covers command syntax, flags, output contract, artifact paths, and workspace layout for all ghidra-agent-cli subcommands. Load when: constructing a ghidra-agent-cli command, interpreting its output, resolving a flag or artifact path question, or debugging CLI behavior. Do not load for P0–P4 workflow sequencing — use the headless-ghidra skill family instead.
- ▌ Headless Ghidra Intake · bytelandtechnology bundleP0 phase skill for Headless Ghidra intake. Use when a target binary/archive needs identity confirmation, workspace initialization, Ghidra discovery, binary inspection, or analysis scope setup before any Ghidra analysis runs.
- ▌ Headless Ghidra Baseline · bytelandtechnology bundleP1 phase skill for Headless Ghidra baseline and runtime evidence. Use after P0 when the target must be imported into Ghidra, auto-analyzed, exported to baseline YAML, and given reproducible runtime or hotpath observations without decompiling function bodies.
- ▌ Headless Ghidra Evidence · bytelandtechnology bundleP2 phase skill for Headless Ghidra third-party evidence. Use after P1 to review baseline/runtime artifacts, identify or rule out third-party code, record pristine sources, classify functions, and capture evidence before metadata recovery.
- ▌ Headless Ghidra Discovery · bytelandtechnology bundleP3 phase skill for Headless Ghidra metadata discovery. Use after P2, or after a P4 batch exposes missing context, to enrich function names, signatures, types, constants, strings, and hotpath metadata in YAML before serialized CLI apply.
- ▌ Headless Ghidra Batch Decompile · bytelandtechnology bundleP4 phase skill for Headless Ghidra selected function substitution. Use after P3 when an approved batch of functions should have metadata applied, be decompiled through Ghidra, and be recorded as per-function capture/substitution YAML.
- ▌ Headless Ghidra Analyze Function · bytelandtechnology bundleThoroughly analyze a single function by first recovering its type definitions, constant definitions, vtables, function name and signature, then producing the final decompilation. Use when the user wants a complete per-function analysis following the strict recovery order: types → constants → vtables → function identity → decompilation.
- ▌ Spec Forge · bytelandtechnology bundleRouter for the spec-forge skill family: initialize a multi-spec `.spec-forge/` YAML collection, detect the earliest incomplete phase for the targeted `spec_id`, enforce hard stage gates, and route broad-to-fine, role-based spec refinement from problem framing through readiness and implementation.
- ▌ Spec Forge CLI · bytelandtechnology bundleUse when the task requires operating or validating the package-local `spec-forge-cli` Rust command surface for initializing workspaces, resolving interactions, mutating YAML artifacts, recording approvals, selecting focus batches, checking gates, advancing stages, or validating UX contracts.
- ▌ Spec Forge Intake · bytelandtechnology bundleUse when you need to turn a rough request into a clear spec framing by defining the problem, stakeholders, scope boundaries, and non-negotiable constraints before solution design begins.
- ▌ Spec Forge Journeys · bytelandtechnology bundleUse when you need to refine user journeys or process flows step by step in small review batches, including states, alternate paths, edge cases, and acceptance detail.
- ▌ Spec Forge Implement · bytelandtechnology bundleUse when you need to execute an approved implementation spec, record what changed, capture validations, and track whether any blockers still prevent completion.
- ▌ Spec Forge Readiness · bytelandtechnology bundleUse when you need to consolidate prior stage artifacts into an implementation-ready spec, confirm completeness, record open assumptions, and decide whether the work is ready to build.
- ▌ Spec Forge Components · bytelandtechnology bundleUse when you need to define component-level contracts in reviewable batches, including responsibilities, interfaces, state, data models, and implementation constraints.
- ▌ Spec Forge Architecture · bytelandtechnology bundleUse when you need to turn approved framing into a top-level solution shape, journey list, and component list before refining detailed flows or implementation contracts.