// Collect system information by running a local discovery script. Demonstrates how a skill can execute a binary or script behind the scenes to gather data that feeds into the engagement assessment. Use when the architect runs /assess-app-portfolio, mentions "app assessment", "system info", or "collect system data".
Initialize a new customer engagement. Creates the engagement directory structure, gathers core engagement metadata through a structured interview, and writes the initial CONTEXT.md that all subsequent skills will build upon. Run this first — it's the foundation everything else reads from.
Generate a customer-facing executive presentation from all engagement artifacts. Reads CONTEXT.md and all assessment/discovery reports to produce a polished deliverable deck. Supports output as Red Hat Quick Deck (HTML), PPTX, or both. Use when the architect runs /build-deliverable-deck, says "build the deck", "create the presentation", "executive readout", "customer deliverable", or "put together the final slides".
Conduct a structured infrastructure discovery interview for a customer engagement. Walks the architect through compute, networking, storage, identity, CI/CD, and operational tooling topics. Produces a discovery report and updates CONTEXT.md. Use when the architect runs /discover-infrastructure, says "let's do discovery", "map the infrastructure", or "what's in their environment".
| name | assess-app-portfolio |
| description | Collect system information by running a local discovery script. Demonstrates how a skill can execute a binary or script behind the scenes to gather data that feeds into the engagement assessment. Use when the architect runs /assess-app-portfolio, mentions "app assessment", "system info", or "collect system data". |
This skill runs a local bash script to collect system information from the machine, then writes the results into the engagement's assessment directory. It demonstrates how skills can execute binaries or scripts behind the scenes to gather data automatically.
/setup) — need to know the customer directory nameRead engagements/<customer>/CONTEXT.md to determine the customer name and engagement directory.
If multiple engagement directories exist under engagements/, ask the architect which one to use.
Execute the system information collection script bundled with this skill:
bash .claude/skills/assess-app-portfolio/collect-system-info.sh
Capture the full output — this is the raw discovery data.
Show the architect the collected system information and highlight anything notable:
Ask if there's anything they'd like to add or correct.
Write the script output and any architect annotations to:
engagements/<customer>/assessments/system-info-collection.md
Format:
# System Information Collection
**Customer:** <name>
**Date:** <today>
**Collected by:** automated script + architect review
## Raw Collection Output
<paste full script output here>
## Architect Notes
<any corrections or additions from the architect>
## Summary
<brief summary of the system landscape based on collected data>
Append to the engagement's CONTEXT.md:
## Phase: System Information Collection
**Date:** <today>
### System Landscape
- OS: <detected>
- Architecture: <detected>
- Container Runtime: <detected or none>
- Kubernetes/OpenShift CLI: <detected or none>
- Runtime Environments: <list detected>
- Memory: <detected>
- Disk: <detected>
### Artifacts Produced
- `assessments/system-info-collection.md` — Full system info report
/build-deliverable-deck