Explorar skills

4845 skills encontradas

Alerta por categoría

Recibe nuevas skills de DevOps e Infra todos los lunes

session-start

0

Briefs the current session by reading session state, handoff doc, and memory to determine the active phase, task, and context budget. Outputs a structured briefing and detects whether the phase should be skipped or reverted based on observable artifacts. Use at the start of every long-running agent session, or when user says "start session", "what are we working on", "resume", "pick up where we le

DevOps e Infrapor ClydeShen

mcpb

0

Generate MCPB (MCP Bundle) packages for MCP server projects. Creates manifest.json, bundle directory structure, validates against the MCPB spec, and wires in CI/CD workflows.

DevOps e Infra#github#gitpor Michelinaunexcused812

consult-commercial

0

Trigger on "consult commercial", "SOW section", "mobilization", "duration and options", "assumptions access env people", "proposal to kickoff", "cadence escalation", "roles RACI consulting". Commercial wrapper: timeboxes, assumptions, path to kickoff. NOT acceptance matrix (use consult-acceptance), NOT exec polish (use consult-package).

DevOps e Infra#aipor Timelnapp

timeln-decided

0

Trigger on "what did I decide about X", "why did I pick X", "did I choose X over Y", "what was my call on X", "ADR for X", "is there a decision on X", "have I picked between X and Y". Use when the user wants to recall a settled past decision, not make a new one. NOT for fresh tradeoff analysis (route to Claude or timeln-find).

DevOps e Infra#aipor Timelnapp

timeln-warned

0

Trigger on "what bit me on X", "have I been burned by X", "gotchas with X", "what went wrong last time with X", "warn me about X", "any retros on X", "past incidents with X". Use when the user wants to sanity-check an approach against their own failure history. NOT for general pitfalls (ask Claude directly) or past decisions (use timeln-decided).

DevOps e Infra#aipor Timelnapp

consult-frame

0

Trigger on "frame the engagement", "consult frame", "problem frame", "scope card", "definition of good", "what decision does this support", "in scope out of scope", "client brief → frame", "one-pager frame". Turns a brief or transcript into a structured engagement frame. NOT the solution arc (use consult-arc), NOT phasing gates (use consult-gates), NOT memory recall (use timeln-find / timeln-decid

DevOps e Infra#aipor Timelnapp

reconcile-impl

0

🤖 My Claude Code config!

DevOps e Infrapor TomerAberbach

consult-acceptance

0

Trigger on "acceptance criteria", "consult acceptance", "success criteria", "signoff matrix", "deliverables per phase", "primary path fallback", "definition of done". Per-phase deliverables, measurable criteria (tech + business/ops), owner, primary path + fallback. NOT commercial terms (use consult-commercial), NOT gate questions (use consult-gates).

DevOps e Infra#aipor Timelnapp

wsl2-browser-setup

0

Install and configure browsers for Windows plus WSL2. Use when a user wants native Linux Chrome inside WSL to work for normal browsing or sign-in flows, or when a tool in WSL needs a Windows host Chrome or Edge instance exposed over CDP. Prefer this skill before any tool-specific browser automation setup.

DevOps e Infra#aipor ArthurZakirov

setup-dell-monitors

0

Troubleshoot Arthur's Dell P2725DE/P2225D monitor setup, especially DisplayPort daisy chaining, "No DP signal from your device" on the P2225D, Windows Fast Startup or shutdown-related display breakage, and reset/reinstall steps for a Lenovo laptop or Dell desktop tower using original Dell cables.

DevOps e Infra#aipor ArthurZakirov

headsup-label

0

Set or change the per-iTerm2-session label — both the window/tab title AND the badge (watermark) for THIS iTerm2 pane only. Use when the user wants a custom name for this specific tab ("call this tab 'deploy debugging'", "label this session 'prod work'", "set the badge to 'frontend'"). Title and badge always share the same string in this skill (the banner and watermark always match). Edits ~/.clau

DevOps e Infra#deploy#aipor wasulajr

classify-change

0

Classify a proposed code change as Leaf Node or Core Code to decide how much AI usage and review rigor is appropriate. Use this skill whenever the user asks "is this leaf or core", "what kind of change is this", "should I vibe code this", "can AI write this", "how rigorous should the review be", or before starting any non-trivial change. Also useful as a sub-step inside other workflows (planning,

DevOps e Infra#aipor appleboy