Cross-reference planned demo features against Elastic platform data to produce a feasibility matrix.
npx skills add https://github.com/ajmeyers42/loom --skill thread-audit
Please help me install this Agent Skill. Skill: thread-audit Source: https://github.com/ajmeyers42/loom/tree/main/skills/thread-audit Command: npx skills add https://github.com/ajmeyers42/loom --skill thread-audit
Cross-references the planned demo scope (from warp-listen output) against the customer's actual Elastic deployment (from warp-scan output, if available) to produce a feature feasibility matrix. Flags version gaps, license tier mismatches, infrastructure requirements, and setup work needed before the demo can be built or run. Outputs a machine-readable audit JSON and a human-readable SE briefing in markdown. ALWAYS use this skill when the user has discovery JSON and wants to know if the planned demo is feasible, asks 'can we demo X on their cluster', 'what do we need to set up before the demo', 'are there any blockers', 'what license do they need for this', or provides both a discovery profile and a diagnostic current-state file. Also trigger when warp-listen output includes gaps referencing version or license unknowns. Run this before weave-script — the audit output shapes what can be scoped.
Provide the discovery JSON and (if available) the current-state JSON to generate a platform audit.
High-intent search queries and answers about installing and using this skill.
A feasibility audit cross-references planned demo scope against the customer's actual Elastic deployment to produce a feature feasibility matrix. It identifies version gaps, license tier mismatches, and infrastructure prerequisites required before building or running the demo.
A partial feasibility audit runs in discovery-only mode when diagnostic current-state data is unavailable. It flags unverified platform items and highlights what must be diagnosed before scoping the demo, outputting both machine-readable JSON and a human-readable SE briefing in Markdown.
Yes, but the audit will flag the license tier as an unverified item and a potential blocker. A full audit mode requires both discovery JSON and current-state diagnostic data to verify license tier mismatches and confirm feature readiness.
Provide discovery JSON and available current-state JSON to generate a platform audit. The audit signals blockers, gaps, and prerequisites for pre-demo readiness by cross-checking planned features against observed Elastic platform capabilities.
The audit outputs a machine-readable platform-audit JSON containing version, license, and infrastructure gating details, alongside a human-readable SE briefing in Markdown that guides pre-demo tasks and highlights blockers.
pathtoresiliencebvModify Warp application settings via JSON schema and TOML files.
ajmeyers42Evaluate Elastic standard demo fit against three criteria and decide predefined or custom path.
HeartcoolmanModify Warp tab configurations from natural language edit requests.
mitchellvandusen-cellAudit Python dependencies for CVEs, outdated packages, licenses, and unused imports.
