abildtoft/kramme:setup
kramme-cc-workflow/skills/kramme:setup/SKILL.md
Run a read-only environment health check for this plugin's local workflow tools, repo context, optional CLIs, and detectable Conductor/worktree state. Use after installing the plugin, when a skill fails because a dependency may be missing, or before running a workflow in a new workspace. Not for installing tools, changing config, or repairing broken environments automatically.
$ install --global
skillsauthnpx skillsauth add abildtoft/kramme-cc-workflow kramme:setupInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 13, 2026, 4:35 AM133.8s3 files scanned
SKILL.md
- name:
- kramme:setup
- description:
- Run a read-only environment health check for this plugin's local workflow tools, repo context, optional CLIs, and detectable Conductor/worktree state. Use after installing the plugin, when a skill fails because a dependency may be missing, or before running a workflow in a new workspace. Not for installing tools, changing config, or repairing broken environments automatically.
- argument-hint:
- [--json|--help]
- disable-model-invocation:
- false
- user-invocable:
- true
Setup Health Check
Run a non-mutating environment check and report what is ready, missing, or only partially detectable.
Workflow
-
Parse
$ARGUMENTS.- No arguments: run the default human-readable report.
--json: request machine-readable output from the script.--help: show script usage.- Unknown arguments: stop and show usage.
-
Run the bundled checker by resolving the script path relative to this skill directory while keeping the current workspace as the command working directory:
"$SKILL_DIR/scripts/check-environment.sh"SKILL_DIRis the directory containing thisSKILL.md. Add--jsonwhen requested. Do notcdinto the skill directory before running it; theContextsection intentionally reports the workspace where the skill was invoked. The checker must not install packages, edit config, fetch remotes, delete files, or write repo-local state. -
Read the report in four groups:
Required: core tools this plugin assumes for broad operation.Recommended: tools used by common PR, verification, and conversion workflows.Optional: tools used only by specific skills or local maintenance paths.Context: repository, Conductor workspace, and local configuration signals.
-
If a tool is missing, provide the install command from the report as guidance only. Install hints assume macOS/Homebrew with Linux (apt) alternates where they exist; adapt to the user's platform and package manager. Do not run installs unless the user explicitly asks in a separate follow-up.
-
For integrations that are not reliably inspectable from the shell, report them as
manual-checkinstead of inventing a status. This includes authenticated app connectors such as Linear and Figma unless their local configuration is directly visible. -
End with a short readiness summary:
Ready: required tools are present.Ready with optional gaps: required tools are present, but recommended or optional tools are missing.Blocked: at least one required tool is missing.
Safety Rules
- Keep the default path read-only.
- Do not auto-install missing tools.
- Do not modify
conductor.json,.worktreeinclude, hook config, shell profiles, or MCP settings. - Treat missing optional integrations as guidance, not failure.
Related Skills
abildtoft/kramme:linear:issue-to-pr
tools
VerifiedTrustedCommunity
Requires Linear MCP. Implements one Linear issue end to end, selects applicable code-review, convention, and PR-refactor gates, runs them to bounded convergence, verifies, and optionally opens the PR and iterates on CI and review feedback until green. Use when the user wants a single Linear issue taken from implementation through a clean Pull Request. Not for implementation-only work, SIW-tracked issues, stacked PRs, existing PR updates, or post-merge rollout.
2SKILL.mdUpdated Jul 28, 2026
abildtoft/kramme:pr:convention-review
development
VerifiedTrustedCommunity
Reviews PR and local changes for convention drift and overcaution against documented rules and mined peer-file practice. Use for new patterns, dependencies, abstractions, or defensive complexity that departs from established practice; every finding cites evidence. Supports --inline. Not for general code quality (use kramme:pr:code-review) or spec review (use kramme:siw:spec-audit --team).
2SKILL.mdUpdated Jul 16, 2026
abildtoft/kramme:siw:wayfinder
testing
VerifiedTrustedCommunity
Charts huge or foggy initiatives into a local `.context` decision map and resolves one typed frontier ticket per session until the work is ready for SIW or another execution workflow. Use when the route to a destination cannot fit in one agent session or parallel workspaces need coordinated planning state. Not for clear specs, ordinary issue decomposition, implementation, or Linear-native tracking.
2SKILL.mdUpdated Jul 11, 2026
abildtoft/kramme:research
development
VerifiedTrustedCommunity
Investigates a question against primary sources and saves one cited Markdown artifact. Use for reading legwork: official docs/API facts, source-code or spec checks, standards, and first-party service behavior before planning or implementation. Not for making product or architecture decisions, implementing code, broad web search, secondary blog summaries, or uncited answers.
2SKILL.mdUpdated Jul 10, 2026