Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

gstack

Estrellas0

Forks0

Actualizado21 de abril de 2026 a las 05:51

Use when the user wants gstack-style execution workflows such as QA, browser dogfooding, code review, debugging, ship or PR preparation, design review, benchmark checks, or deployment verification. This packet-owned wrapper is installable into ~/.agents/skills, ~/.codex/skills, and ~/.claude/skills.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

kingkillery

kingkillery/pi-config

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de garantía de calidad de software y probadoresOcupaciones informáticas y matemáticas·SOC 15-1253

Explorador de archivos

3 archivos

SKILL.md

readonly

name	gstack
description	Use when the user wants gstack-style execution workflows such as QA, browser dogfooding, code review, debugging, ship or PR preparation, design review, benchmark checks, or deployment verification. This packet-owned wrapper is installable into ~/.agents/skills, ~/.codex/skills, and ~/.claude/skills.

gstack

This is the packet-owned home-skill wrapper for gstack.

Startup

Read repo-local instructions first.
If you are inside an llm-wiki-memory workspace, read AGENTS.md, LLM_WIKI_MEMORY.md, and .llm-wiki/config.json before acting.
Detect whether a richer external gstack bundle is installed.

A richer bundle is any gstack folder that contains runtime or subskill content beyond this wrapper, for example bin/, browse/, qa/, review/, or multiple sibling skill folders.

Check these locations in order:

~/.codex/skills/gstack
~/.claude/skills/gstack
~/.agents/skills/gstack
repo-local .codex/skills/gstack
repo-local .claude/skills/gstack
repo-local .agents/skills/gstack

If you find a richer bundle, read the relevant upstream SKILL.md there and use it.

If you do not find one, continue with this wrapper and execute the workflow directly with native tools and subagents.

Workflow Routing

QA, site testing, browser dogfooding: reproduce the flow, capture evidence, then fix or report.
Code review: findings first, severity ordered, with file references and missing-test risks.
Investigation: reproduce, isolate root cause, patch minimally, verify the fix.
Ship or PR prep: run the relevant checks, summarize risk, and only push or open a PR when asked.
Design or DX review: inspect the real surface, not just source code.

Packet Integration

Prefer packet helpers before guessing:
- scripts/setup_llm_wiki_memory.ps1
- scripts/setup_llm_wiki_memory.sh
- scripts/check_llm_wiki_memory.ps1
- scripts/check_llm_wiki_memory.sh
Prefer packet retrieval and memory surfaces when they are available:
- pk-qmd
- llm-wiki-skills
- brv
- GitVizz

Constraints

Do not assume external gstack binaries exist. Verify before invoking them.
If a missing external runtime blocks a richer workflow, name the missing path or tool explicitly and fall back when possible.
Keep the response concrete: workflow used, evidence gathered, files changed, next action.

Más de este repositorio

mismo repositorio

codechat

kingkillery/pi-config

Voice-driven code agent. Talk to your codebase in natural language with speech-friendly responses. Triggers on "codechat", "voice chat about code", "talk to my codebase", or "chat about code".

2026-04-210

g-kade

kingkillery/pi-config

Use when the user wants the KADE plus gstack bridge, including session kickoff with user-profile context, /g-kade install style project scaffolding, repo adaptation, or structured handoff logging tied to llm-wiki-memory packet setup. This packet-owned wrapper is installable into ~/.agents/skills, ~/.codex/skills, and ~/.claude/skills.

2026-04-210

impeccable-frontend-design

kingkillery/pi-config

Create distinctive, production-grade interfaces with high design quality using the Impeccable frontend vocabulary. Use when designing polished web or Android app experiences, especially when the user wants stronger visual taste, clearer UX, or a more memorable aesthetic.

2026-04-210

kade-hq

kingkillery/pi-config

Use when the user wants the KADE System itself, including Layer 1 and Layer 2 context loading, KADE session structure, HUMAN.md and kade/ overlays, or project initialization and handoff workflows. This packet-owned wrapper is installable into ~/.agents/skills, ~/.codex/skills, and ~/.claude/skills.

2026-04-210

msi-skill-sync

kingkillery/pi-config

Sync agent skills from a canonical source directory into one or more Obsidian vaults or project workspaces. Compares skill directories by file count and total size, reports new/updated/vault-only skills, then copies everything from canonical into the target while preserving target-only skills. Triggers on "sync skills", "update skills", "skill sync", "refresh skills", "pull latest skills", "sync vault skills", "check for skill updates", or "are my skills up to date".

2026-04-210

nlm-skill

kingkillery/pi-config

Expert guide for the NotebookLM CLI (`nlm`) and MCP server - interfaces for Google NotebookLM. Use this skill when users want to interact with NotebookLM programmatically, including: creating/managing notebooks, adding sources (URLs, YouTube, text, Google Drive), generating content (podcasts, reports, quizzes, flashcards, mind maps, slides, infographics, videos, data tables), conducting research, chatting with sources, or automating NotebookLM workflows. Triggers on mentions of "nlm", "notebooklm", "notebook lm", "podcast generation", "audio overview", or any NotebookLM-related automation task.

2026-04-210

name	gstack
description	Use when the user wants gstack-style execution workflows such as QA, browser dogfooding, code review, debugging, ship or PR preparation, design review, benchmark checks, or deployment verification. This packet-owned wrapper is installable into ~/.agents/skills, ~/.codex/skills, and ~/.claude/skills.

gstack

This is the packet-owned home-skill wrapper for gstack.

Startup

Read repo-local instructions first.
If you are inside an llm-wiki-memory workspace, read AGENTS.md, LLM_WIKI_MEMORY.md, and .llm-wiki/config.json before acting.
Detect whether a richer external gstack bundle is installed.

A richer bundle is any gstack folder that contains runtime or subskill content beyond this wrapper, for example bin/, browse/, qa/, review/, or multiple sibling skill folders.

Check these locations in order:

~/.codex/skills/gstack
~/.claude/skills/gstack
~/.agents/skills/gstack
repo-local .codex/skills/gstack
repo-local .claude/skills/gstack
repo-local .agents/skills/gstack

If you find a richer bundle, read the relevant upstream SKILL.md there and use it.

If you do not find one, continue with this wrapper and execute the workflow directly with native tools and subagents.

Workflow Routing

QA, site testing, browser dogfooding: reproduce the flow, capture evidence, then fix or report.
Code review: findings first, severity ordered, with file references and missing-test risks.
Investigation: reproduce, isolate root cause, patch minimally, verify the fix.
Ship or PR prep: run the relevant checks, summarize risk, and only push or open a PR when asked.
Design or DX review: inspect the real surface, not just source code.

Packet Integration

Prefer packet helpers before guessing:
- scripts/setup_llm_wiki_memory.ps1
- scripts/setup_llm_wiki_memory.sh
- scripts/check_llm_wiki_memory.ps1
- scripts/check_llm_wiki_memory.sh
Prefer packet retrieval and memory surfaces when they are available:
- pk-qmd
- llm-wiki-skills
- brv
- GitVizz

Constraints

Do not assume external gstack binaries exist. Verify before invoking them.
If a missing external runtime blocks a richer workflow, name the missing path or tool explicitly and fall back when possible.
Keep the response concrete: workflow used, evidence gathered, files changed, next action.