Source profileQuality 86/100Review permissions

kirodotdev/KiroCrew/skills/kirocrew-commands/SKILL.md

kirocrew-commands

Complete CLI reference for KiroCrew commands. Use for help, commands, setup, how to, what can you do, getting started, onboarding.

Source repository stars
1,286
Declared platforms
0
Static risk flags
3
Last source update
2026-08-06
Source checked
2026-08-06

Decision brief

What it does—and where it fits

Complete CLI reference for KiroCrew commands. Use for help, commands, setup, how to, what can you do, getting started, onboarding.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/kirodotdev/KiroCrew --skill "skills/kirocrew-commands"
    Safe inspection promptEditorial

    Inspect the Agent Skill "kirocrew-commands" from https://github.com/kirodotdev/KiroCrew/blob/5bcf51037a10a420d51a290b505245a3e6f0b1ee/skills/kirocrew-commands/SKILL.md at commit 5bcf51037a10a420d51a290b505245a3e6f0b1ee. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Setup & System

      Review the “Setup & System” section in the pinned source before continuing.

      Review and apply the “Setup & System” source section.
    2. 02

      Gateway (Server)

      Review the “Gateway (Server)” section in the pinned source before continuing.

      Review and apply the “Gateway (Server)” source section.
    3. 03

      Service Management

      Review the “Service Management” section in the pinned source before continuing.

      Review and apply the “Service Management” source section.
    4. 04

      Pods (Isolated Worktree Test Instances)

      Ephemeral, full-stack KiroCrew gateways — one per feature worktree — that run on their own port + isolated KIROCREWHOME and never touch the live :5476 gateway or shared data. Linux systemd --user only. is a worktree name (resolved by directory basename or feat/ branch convention…

      Ephemeral, full-stack KiroCrew gateways — one per feature worktree — that run on their own port + isolated KIROCREWHOME and never touch the live :5476 gateway or shared data. Linux systemd --user only. is a worktree nam…Platform: Linux only. On macOS/Windows every systemd-touching verb refuses with a one-line message pointing at ./dev-backend.sh — it does not crash, and pod install writes no unit file. pod url works anywhere (pure comp…Port derivation: base + (cksum(name) % 199) + 1 (base 7810 → 7811..8009). Override with PORT= in /.kiro/crew/pods/.env.
    5. 05

      Dashboard Access

      Review the “Dashboard Access” section in the pinned source before continuing.

      Review and apply the “Dashboard Access” source section.

    Permission review

    Static risk signals and limitations

    Runs scripts

    medium · line 65

    The documentation asks the agent to run terminal commands or scripts.

    | `kirocrew pod exec <wt> -- <args>` | Run a kirocrew command against a pod, using the pod's own binary and data |

    Runs scripts

    medium · line 148

    The documentation asks the agent to run terminal commands or scripts.

    | `kirocrew cron preview SCRIPT` | Run a script cron locally with real MCP tools; notifications are printed, not delivered |

    Writes files

    medium · line 186

    The documentation asks the agent to create, modify, or delete local files.

    | `kirocrew artifact save --name "My Widget" --content-file widget.html` | Save new artifact |

    Writes files

    medium · line 188

    The documentation asks the agent to create, modify, or delete local files.

    | `kirocrew artifact update SLUG --content-file widget.html` | Update artifact content |

    Reads files

    low · line 244

    The documentation asks the agent to read local files, directories, or repositories.

    | `kirocrew config set --file config.json` | Load full config from JSON file |

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score86/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars1,286SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    kirodotdev/KiroCrew
    Skill path
    skills/kirocrew-commands/SKILL.md
    Commit
    5bcf51037a10a420d51a290b505245a3e6f0b1ee
    License
    Apache-2.0
    Collected
    2026-08-06
    Default branch
    main
    View the original SKILL.md

    KiroCrew CLI Reference

    Setup & System

    CommandDescription
    kirocrew setupInteractive wizard — install agent config and configure credentials
    kirocrew setup --agent-onlyOnly install kiro-cli agent config, skip credential prompts
    kirocrew setup --cleanFresh install — don't merge from existing config
    kirocrew doctorVerify KiroCrew setup (checks all dependencies)
    kirocrew updateUpdate KiroCrew to the latest version
    kirocrew --versionPrint installed version

    Gateway (Server)

    CommandDescription
    kirocrew gatewayStart dashboard + Slack gateway
    kirocrew gateway --slack-onlySlack only — skip dashboard web server
    kirocrew gateway --no-cronsSkip cron scheduler
    kirocrew gateway --port 9999Override dashboard port
    kirocrew gateway --port autoOS-assigned ephemeral port
    kirocrew gateway --no-openDon't auto-open dashboard URL in browser
    kirocrew gateway --approval readsAuto-approve read-only tools
    kirocrew gateway --approval yoloAuto-approve all tools (requires isolated KIROCREW_HOME)
    kirocrew gateway --approval interactivePrompt for every tool (default)
    kirocrew gateway --seed FIXTURESeed $KIROCREW_HOME from fixture before starting (dev)
    kirocrew gateway --test-modeAlias for --port auto --no-open --json-ready --approval reads
    kirocrew stopStop a running gateway
    kirocrew stop --port 9999Stop gateway on specific port
    kirocrew restartRestart gateway (service-aware)
    kirocrew statusShow runtime stats (uptime, sessions, crons, lessons)

    Service Management

    CommandDescription
    kirocrew service installInstall and start as system service (sudo on Linux)
    kirocrew service uninstallStop and remove system service
    kirocrew service statusShow service status (systemctl/launchctl)
    kirocrew logsShow gateway logs (last 100 lines)
    kirocrew logs -fFollow (tail) live log output
    kirocrew logs -n 50Show last N lines

    Pods (Isolated Worktree Test Instances)

    Ephemeral, full-stack KiroCrew gateways — one per feature worktree — that run on their own port + isolated KIROCREW_HOME and never touch the live :5476 gateway or shared data. Linux systemd --user only. <wt> is a worktree name (resolved by directory basename or feat/<name> branch convention).

    CommandDescription
    kirocrew pod installLay down the systemd --user template unit (once per machine)
    kirocrew pod provision <wt>Build the worktree's venv + SPA dist (the on-ramp)
    kirocrew pod up <wt>Bring up an isolated pod (auto-builds venv; fails if dist missing)
    kirocrew pod up <wt> --provisionProvision (venv + dist build) then bring up
    kirocrew pod up <wt> --jsonBring up and print {base_url, token, port} as JSON
    kirocrew pod lsList running pods
    kirocrew pod status <wt>Up/down + health for one pod
    kirocrew pod token <wt>(Re)mint a dashboard token for a running pod
    kirocrew pod url <wt>Print the pod's base URL
    kirocrew pod logs <wt> -n NTail the pod's journal
    kirocrew pod down <wt>Evict the pod and delete its isolated HOME
    kirocrew pod exec <wt> -- <args>Run a kirocrew command against a pod, using the pod's own binary and data

    Platform: Linux only. On macOS/Windows every systemd-touching verb refuses with a one-line message pointing at ./dev-backend.sh — it does not crash, and pod install writes no unit file. pod url works anywhere (pure computation).

    Port derivation: base + (cksum(name) % 199) + 1 (base 78107811..8009). Override with PORT= in ~/.kiro/crew/pods/<name>.env.

    See src/kiro_crew/pod/README.md for the full reference.

    Dashboard Access

    CommandDescription
    kirocrew tokenPrint a dashboard URL with auth token (TTL: 20h)
    kirocrew token --ttl 1hToken with custom TTL (e.g. 1h, 30m)
    kirocrew logoutRevoke all active dashboard sessions
    kirocrew manifestGenerate Slack app manifest with your alias
    kirocrew manifest --urlPrint one-click Slack app creation URL

    Chat

    CommandDescription
    kirocrew chatInteractive chat (REPL mode)
    kirocrew chat -m "message"Single message (non-interactive)
    kirocrew chat --model claude-opusUse specific model

    Browsing (Playwright MCP)

    Browsing uses Playwright MCP tools, not kirocrew CLI. The kirocrew browse subcommands manage auth only.

    CommandDescription
    kirocrew browse setupInstall Playwright MCP + browsers
    kirocrew browse auth healthCheck browser auth / cookie status (prints JSON)
    kirocrew browse auth refreshWrite Playwright storage state from an exported cookie jar

    Browsing workflow: Load the browser-auth skill (or follow it directly):

    1. kirocrew browse auth health — check auth; if unhealthy or no cookies, tell the user to export a fresh cookie jar from a browser where they're logged in
    2. kirocrew browse auth refresh — write Playwright storage state from the exported cookie jar (pre-loads auth into the browser context)
    3. Use Playwright MCP tools: browser_navigate, browser_snapshot, browser_click, browser_fill_form, browser_take_screenshot, browser_evaluate
    4. On a 401 / login redirect, the session cookies expired — the user re-exports the cookie jar and you re-run kirocrew browse auth refresh

    Note: Playwright auto-installs during kirocrew setup.

    Autonomous Task Runner

    CommandDescription
    kirocrew run TASK.mdRun a task spec file (auto-resumes from checkpoint)
    kirocrew run TASK.md --freshStart from scratch, ignore checkpoint
    kirocrew run TASK.md --no-testSkip build/test verification after each step
    kirocrew run TASK.md --timeout 3600Set global timeout in seconds
    kirocrew run TASK.md --name "My Task"Override human-readable task name

    Subagents

    CommandDescription
    kirocrew spawn run "task"Spawn a background subagent (wait for result)
    kirocrew spawn run --async "task"Fire-and-forget subagent
    kirocrew spawn listList active subagents

    Cron Jobs

    CommandDescription
    kirocrew cron listList all cron jobs
    kirocrew cron add NAME MESSAGE --every 3600Add job with interval (seconds)
    kirocrew cron add NAME MESSAGE --cron "0 9 * * MON-FRI"Add job with cron expression
    kirocrew cron add NAME MESSAGE --agent myagentAdd job for specific agent
    kirocrew cron add NAME MESSAGE --approval-mode autoAdd job with auto tool approval
    kirocrew cron add NAME MESSAGE --channel C123456Post results to Slack channel
    kirocrew cron update JOB_ID --message "new msg"Update job message
    kirocrew cron update JOB_ID --agent myagentUpdate job agent
    kirocrew cron update JOB_ID --approval-mode autoSet auto-approval
    kirocrew cron update JOB_ID --approval-mode defaultReset approval to default
    kirocrew cron remove JOB_IDRemove a cron job
    kirocrew cron pause JOB_IDPause a cron job
    kirocrew cron resume JOB_IDResume a paused job
    kirocrew cron trigger JOB_IDTrigger a job immediately
    kirocrew cron preview SCRIPTRun a script cron locally with real MCP tools; notifications are printed, not delivered
    kirocrew cron preview SCRIPT -m "msg" -e K=VPreview with an input message / extra env vars

    Learning & Memory

    CommandDescription
    kirocrew learn listList all saved lessons
    kirocrew learn add "rule text"Save a lesson (category: knowledge)
    kirocrew learn add "rule text" --category toolSave with category (tool/preference/knowledge)
    kirocrew learn add "rule text" --negative "avoid X"Save with negative example
    kirocrew learn remove "query"Remove lessons matching substring
    kirocrew memory listShow semantic memory entries
    kirocrew memory search "query"Search episodic memories
    kirocrew memory statsShow memory statistics
    kirocrew memory auditScan memory for suspicious content
    kirocrew memory exportExport all memory to JSON (stdout)
    kirocrew memory export -o file.jsonExport to file
    kirocrew memory import file.jsonImport memory from JSON
    kirocrew memory migrateMigrate legacy markdown memory to vector store
    kirocrew knowledge dedupPreview cross-source duplicate knowledge documents (dry-run)
    kirocrew knowledge dedup --applyActually collapse the duplicates
    kirocrew consolidateList sessions with unconsolidated messages
    kirocrew consolidate SESSION_KEYForce consolidate a session (triggers auto-skill extraction)
    kirocrew consolidate --allConsolidate all pending sessions

    Artifacts

    LLM-generated UI components (widgets, HTML, markdown, SVG, JSON, text).

    CommandDescription
    kirocrew artifact listList all artifacts
    kirocrew artifact list --tag ops --kind widgetFilter by tag and kind
    kirocrew artifact list -q "CR"Substring filter on name
    kirocrew artifact show SLUGPrint artifact content
    kirocrew artifact show SLUG --version 2Show specific version
    kirocrew artifact show SLUG --metaShow metadata as JSON
    kirocrew artifact save --name "My Widget" --content-file widget.htmlSave new artifact
    kirocrew artifact save --name "X" --content "..." --tags ops,crSave with inline content
    kirocrew artifact update SLUG --content-file widget.htmlUpdate artifact content
    kirocrew artifact update SLUG --name "New Name" --tags opsRename/retag
    kirocrew artifact versions SLUGList version numbers
    kirocrew artifact delete SLUGDelete artifact and all versions

    Agents & Workspaces

    CommandDescription
    kirocrew agent listList KiroCrew agents
    kirocrew agent create --name NAMECreate a new agent
    kirocrew agent create --name NAME --kiro-agent kirocrew --workspace defaultFull options
    kirocrew agent update NAME --kiro-agent new-agentUpdate agent settings
    kirocrew agent delete NAMEDelete an agent
    kirocrew workspace listList workspaces
    kirocrew workspace create --name NAME --dir DIRNAMECreate workspace (--dir is a name under the data home, not an absolute path)
    kirocrew workspace create --name NAME --copy-from existingCopy from existing
    kirocrew workspace update NAME --dir DIRNAMEUpdate workspace dir (same containment rule)
    kirocrew workspace delete NAMEDelete workspace

    On the CLI, --dir must resolve to a strict descendant of $KIROCREW_HOME (default ~/.kiro/crew): anything landing outside — /tmp/x, ../x, ~/x — is refused with a SEL denied audit event, and so is the data home root itself (in any spelling: absolute, ~/.kiro/crew, ., or empty), since a workspace there would put agent-writable memory on top of config.json and .env. The test is containment, not "is it absolute": an absolute path landing under the home is accepted, since it resolves where the relative form would. Pass workspace-myproject, not /path/to/dir.

    Note the surface difference: the dashboard POST /api/workspaces DOES accept an absolute dir (screened by is_sensitive_path, so ~/.ssh / ~/.aws / keystone paths are still refused). The CLI is the stricter of the two.

    Apps

    CommandDescription
    kirocrew app listList installed apps
    kirocrew app install /path/to/app-dirInstall app from local directory (needs app.json)
    kirocrew app enable NAMEEnable an installed app
    kirocrew app disable NAMEDisable an installed app
    kirocrew app uninstall NAMEUninstall an app and preserve its data directory
    kirocrew app uninstall NAME --purge-dataUninstall and explicitly delete the app data directory
    kirocrew app info NAMEShow app details
    kirocrew app init NAMEScaffold a new app (kebab-case name)
    kirocrew app init NAME --backend --ui --cronScaffold with backend, UI, and sample cron
    kirocrew app dev NAMEToggle an app into dev mode (no-store UI serving + live reload on file change)
    kirocrew app dev NAME --offLeave dev mode

    Configuration

    CommandDescription
    kirocrew config getShow all config
    kirocrew config get agent.providerGet specific value (dot-separated key)
    kirocrew config set dashboard.url http://localhost:5476Set a config value (port is the KIROCREW_PORT env var, not a config key)
    kirocrew config set --file config.jsonLoad full config from JSON file
    kirocrew config editOpen config in $EDITOR

    Profiling (debug-only)

    Off unless KIROCREW_DEBUG=1 is set; the CLI is the only entry point. Emits folded stacks (open in speedscope / flamegraph.pl). See docs/architecture/design-notes/profiling.md.

    CommandDescription
    KIROCREW_DEBUG=1 kirocrew perf sample --call mod:fnProfile that callable in-process (no extra dependency)
    KIROCREW_DEBUG=1 kirocrew perf sampleAttach to the running gateway (needs pip install "kirocrew[perf]")
    KIROCREW_DEBUG=1 kirocrew perf sample --pid 1234 --seconds 30Attach to a specific PID for N seconds (1-300)
    ... --interval 0.002Seconds between samples (0.001-1.0, default 0.005)
    ... --output /tmp/p.foldedWhere to write the profile (default ./kirocrew-profile.folded)
    KIROCREW_DEBUG=1 kirocrew desktop metricsPer-process CPU/memory of the Electron app (--json, --top N, --path)

    On macOS the attach path additionally needs elevated privileges (the OS denies task_for_pid), so it may require sudo; --call needs neither py-spy nor sudo.

    desktop metrics reads a recording rather than querying the app: getAppMetrics() is Electron-main-only, so the app samples itself into an artifact when started with KIROCREW_DEBUG set. Setting the variable only for the CLI does not make an already-running app record -- restart it.

    Security & Eval

    CommandDescription
    kirocrew security auditScan conversation history for suspicious tool usage
    kirocrew security deny-listShow active deny patterns
    kirocrew security eventsShow recent security event log entries (last 20)
    kirocrew security events -n 50Show N entries
    kirocrew security verifyVerify security event log HMAC integrity
    kirocrew evalRun smoke test evaluation (~30s)
    kirocrew eval memory_recall_basicRun specific scenario by name
    kirocrew eval --allRun all scenarios (slow)
    kirocrew eval --judgeEnable LLM judge scoring

    Governance Policy (read-only)

    Inspects the two-level security model (effective = POLICY ∩ PROFILE, tightest-wins). All four verbs are read-only — the enterprise ceiling is never edited through the CLI (its files are keystone-fenced so the agent cannot read or write them).

    CommandDescription
    kirocrew policy showShow the effective enterprise security policy
    kirocrew policy validateLoad-check the policy + all profiles
    kirocrew policy explain SCOPE ITEMExplain one tool/scope decision for a surface
    kirocrew policy explain SCOPE ITEM --session-key K --agent A --app APPScope the explanation to a surface
    kirocrew policy profile NAMEShow a profile by name

    Cloud (Bring-Your-Own AWS)

    Runs KiroCrew on an EC2 instance in your own AWS account; credentials are resolved by the aws CLI and never stored by KiroCrew. All verbs accept --profile / --region; the single-instance verbs also accept --tag (defaults to the last launched instance).

    CommandDescription
    kirocrew cloud doctorCheck cloud prerequisites + AWS reachability
    kirocrew cloud launchProvision + configure an instance (interactive)
    kirocrew cloud launch --size TIER -yNon-interactive launch at a size tier
    kirocrew cloud launch --newCreate a separate new instance instead of resuming the saved one
    kirocrew cloud launch --keep-on-failureOn bootstrap failure keep the instance for inspection
    kirocrew cloud listList your KiroCrew cloud instances
    kirocrew cloud statusShow one instance's state
    kirocrew cloud connectOpen the dashboard over an SSM tunnel
    kirocrew cloud tunnelOpen the dashboard SSM tunnel (standalone alias of connect)
    kirocrew cloud connect --local-port N --no-browserForward to a specific local port, no browser
    kirocrew cloud loginSign kiro-cli in on the instance (fixes "not logged in" chat errors)
    kirocrew cloud stopStop the instance (pause billing)
    kirocrew cloud startStart a stopped instance
    kirocrew cloud destroyRemove the instance and ALL its AWS resources
    kirocrew cloud destroy --dry-runShow the delete command without running it
    kirocrew cloud iam-policyPrint the least-privilege IAM policy to apply
    kirocrew cloud iam-boundaryPre-create the immutable permissions boundary (admin, one-time)

    Computer Use (Desktop Automation)

    Default-OFF behind a keystone enable (~/.kiro/crew/computer_use.json, not config.json). macOS only. These are human debug/diagnostic twins of the computer_* MCP tools — the agent uses the MCP tools, not these.

    CommandDescription
    kirocrew computer doctorReport platform support, keystone enable state, and the advisory Accessibility / Screen Recording probe
    kirocrew computer doctor --jsonSame as JSON
    kirocrew computer appsList on-screen applications the accessibility layer can address
    kirocrew computer call TOOL k=v …Run ONE computer-use tool through the same gated chokepoint the agent uses
    kirocrew computer call --calls '[…]'Run a JSON array of calls in a SINGLE process, so element_index values stay resolvable

    Snapshot & Restore

    CommandDescription
    kirocrew snapshotCreate a portable backup of KiroCrew state
    kirocrew snapshot /path/to/dirSnapshot to specific output directory
    kirocrew snapshot --keep 7Keep N most recent snapshots (default: 7)
    kirocrew snapshot --listList existing snapshots
    kirocrew restoreRestore from most recent snapshot
    kirocrew restore /path/to/snap.tar.gzRestore from specific snapshot
    kirocrew restore --mode replaceReplace mode (default)
    kirocrew restore --mode mergeMerge mode
    kirocrew restore --dry-runPreview without applying
    kirocrew restore --components memory,cronsRestore specific components only
    kirocrew restore --list-componentsList restorable components
    kirocrew restore --forceRestore even if gateway is running

    Slack Commands

    All Allowed Users

    CommandDescription
    !dashboardGet a presigned dashboard link (DM'd to you). Link expires in 5 min; session lasts 1h
    !dashboard 2hDashboard link with custom duration (accepts <N>h or <N>m, max 6h)
    /kirocrew dashboardSame via slash command
    /kirocrew helpList available slash sub-commands
    !stopForce-halt the current agent turn (bypasses semaphore, cancels active task)
    statusShow runtime stats
    pingAuto-reply pong
    cron listList cron jobs
    run <path>Run an autonomous task from a spec file

    Owner-Only Slash Commands

    CommandDescription
    /kirocrew yoloToggle YOLO mode (auto-approve all tool calls)
    /kirocrew agentShow agent selector dropdown
    /kirocrew agent <name>Switch to named agent
    /kirocrew voiceOpen TTS voice settings modal
    /kirocrew configOpen config modal
    /kirocrew usersOpen allowed users management modal
    /kirocrew channelsOpen tracked channels modal
    /kirocrew sessionsList recent sessions with resume/end buttons

    Environment Variables

    VariablePurposeDefault
    KIROCREW_HOMEOverride config/data directory~/.kiro/crew
    KIROCREW_PORTOverride dashboard port5476
    KIROCREW_PROJECT_DIROverride agent config/skills directoryAuto-detected
    KIROCREW_POD_REPORepo to resolve worktree names frominvoking cwd
    KIROCREW_POD_ROOTIsolated pod HOMEs (nuked on stop)~/.kirocrew-pods
    KIROCREW_POD_BASE_PORTPort derivation base7810
    KIROCREW_POD_LIVE_PORTPort a pod must never bind5476

    Alternatives

    Compare before choosing

    Computed 10043,183

    coreyhaines31/marketingskills

    ab-testing

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

    Computed 10023,881

    alirezarezvani/claude-skills

    app-store-optimization

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

    Computed 1004,969

    dotnet/skills

    migrate-vstest-to-mtp

    Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing

    Computed 100148

    JasonColapietro/suede-creator-skills

    suede-ab-testing

    Suede-owned experimentation discipline for hypotheses, sample sizing, test duration, significance, and repeatable experiment programs. Use when comparing variants, deciding whether a result is reliable, or building an experiment backlog and cadence. NOT FOR: analytics instrumentation (use suede-analytics), post-click conversion diagnosis (use suede-site-alchemy), or writing the variant copy itself (use suede-copy).