executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
runtime-setupInstall, import, and diagnose the Giskard OSS split-package runtime and core utilities.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task is about installing Giskard, choosing optional
extras, importing the v3 split packages, disabling telemetry, diagnosing package
namespace conflicts, or using the small utilities exported by giskard.core.
giskard.core utility contracts.giskard[...] extra do I need?"import giskard_checks fail?"import giskard.core reporting a legacy package conflict?"MinIntervalRateLimiter, Discriminated, or Error."Handle here:
scan, provider, LiteLLM, checks, and scanner extras.giskard.core,
giskard.agents, giskard.llm, giskard.checks, and giskard.scan.giskard meta-distribution/shim and legacy package conflict.DO_NOT_TRACK, GISKARD_TELEMETRY_DISABLED, and
disable_telemetry().giskard.core utilities: rate limiters, discriminated unions, serializable
errors, version helpers, and telemetry context helpers.Route elsewhere:
KnowledgeBase, scan generators, and
third-party scanner integrations: scan-redteam.Set telemetry opt-out environment variables before the first giskard.* import
when a user asks for privacy-first execution. Use installed-package imports and
self-contained smoke checks; do not depend on a source checkout being present.