goodmorning
a skill to boot up developer tools to latest and greatest for the day
Good morning setup
When the developer says "goodmorning" let's explain that you are going to help with developer laptop setup to the latest tools.
Update and install the latest developer tools to start your day.
Complete all Phases to ensure your development environment is up-to-date.
Prerequisites
Before running this skill, ensure you have:
-
Authenticated GitHub CLI session - Required for Phase 0 and Phase 2 (downloading OTC release assets from GitHub releases)
- Run
gh auth loginif the CLI is not already authenticated - The authenticated session must have authorization to the
optum-tech-computeorganization - For CI or headless shells, export
GH_TOKENwith an organization-authorized token instead - Verify with:
gh auth status
- Run
-
VS Code and VS Code Insiders installed - Required for Phase 0
-
Homebrew installed - Required for Phase 1 (Codex installation), Phase 3 (Claude CLI installation), and Phase 4 (gh installation)
Phase 0: Install the latest VS Code extension
Step 1: Download the latest release
cd /tmp && gh release download --repo optum-tech-compute/otc-awesome-llm --pattern "otc-awesome-llm.vsix" --clobber
Step 2: Install the extension to both VS Code and VS Code Insiders
code --install-extension /tmp/otc-awesome-llm.vsix && codeinsiders --install-extension /tmp/otc-awesome-llm.vsix
Verify installation
code --list-extensions | grep otc-awesome-llm
codeinsiders --list-extensions | grep otc-awesome-llm
Restart VS Code and VS Code Insiders, then confirm the OTC Awesome LLM icon appears in the activity bar.
Note: Sideloaded VSIX extensions do not auto-update. Re-run this phase to pick up new releases.
Phase 1: Install or upgrade Codex
1. Update Homebrew
brew update
2. Install or upgrade Codex
brew install codex || brew upgrade codex
3. Remove macOS quarantine (if needed)
After installing or upgrading Codex, macOS may block the binary with a quarantine flag. If you see a Gatekeeper warning when running codex, remove the quarantine attribute:
xattr -d com.apple.quarantine "$(command -v codex)"
For the full quarantine removal procedure (including UI and verification steps), see the codex-remove-quarantine skill in this repository:
- Path:
shared/skills/codex-remove-quarantine/SKILL.md - Repo: optum-tech-compute/otc-awesome-llm
4. Verify
codex --version
Phase 2: Install or refresh the OTC Codex marketplace plugin
Run the Phase 2 commands in the same shell so the release asset variables are preserved.
Step 1: Confirm the latest release has a Codex marketplace archive
gh release view --repo optum-tech-compute/otc-awesome-llm --json tagName,assets
OTC_CODEX_PLUGIN_ASSET="$(gh release view --repo optum-tech-compute/otc-awesome-llm --json assets --jq '.assets[].name | select(startswith("otc-awesome-llm-codex-plugin-") and endswith(".zip"))' | head -n 1)"
If OTC_CODEX_PLUGIN_ASSET is empty, report that the latest OTC Awesome LLM release is missing the Codex marketplace ZIP and continue with the remaining phases.
Step 2: Download and extract the marketplace archive
if [ -n "$OTC_CODEX_PLUGIN_ASSET" ]; then
OTC_CODEX_PLUGIN_ROOT="${CODEX_HOME:-$HOME/.codex}/.tmp/otc-awesome-llm-codex-plugin"
OTC_CODEX_PLUGIN_ZIP="/tmp/$OTC_CODEX_PLUGIN_ASSET"
gh release download --repo optum-tech-compute/otc-awesome-llm --pattern "otc-awesome-llm-codex-plugin-*.zip" --dir /tmp --clobber
: "${OTC_CODEX_PLUGIN_ROOT:?OTC_CODEX_PLUGIN_ROOT must be set}"
case "$OTC_CODEX_PLUGIN_ROOT" in
"$HOME"/.codex/*|"$HOME"/.codex) ;;
*) echo "refusing rm -rf outside ~/.codex: $OTC_CODEX_PLUGIN_ROOT" >&2; exit 1 ;;
esac
rm -rf "$OTC_CODEX_PLUGIN_ROOT"
mkdir -p "$OTC_CODEX_PLUGIN_ROOT"
unzip -q "$OTC_CODEX_PLUGIN_ZIP" -d "$OTC_CODEX_PLUGIN_ROOT"
fi
Step 3: Validate and register the marketplace
if [ -n "$OTC_CODEX_PLUGIN_ASSET" ]; then
if [ ! -f "$OTC_CODEX_PLUGIN_ROOT/.agents/plugins/marketplace.json" ] || [ ! -f "$OTC_CODEX_PLUGIN_ROOT/plugins/drzero/.codex-plugin/plugin.json" ]; then
echo "Downloaded OTC Codex marketplace archive is missing required plugin files. Continue with the remaining phases."
else
codex plugin marketplace add "$OTC_CODEX_PLUGIN_ROOT" || codex plugin marketplace upgrade otc-awesome-llm
fi
fi
Restart or reload Codex after this phase so Codex can discover the drzero plugin and its bundled skills.
Phase 3: Install or upgrade Claude CLI
1. Install or upgrade Claude Code
Use the Homebrew cask to match the repository's Claude Code setup guidance.
brew install --cask claude-code || brew upgrade --cask claude-code
2. Remove macOS quarantine (if needed)
After installing or upgrading Claude Code, macOS may block the binary with a quarantine flag. If you see a Gatekeeper warning when running claude, remove the quarantine attribute:
xattr -d com.apple.quarantine "$(command -v claude)"
3. Verify
claude --version
Phase 4: Install or upgrade gh
1. Update Homebrew
brew update
2. Install or upgrade gh
brew install gh || brew upgrade gh
Related Assets
skills-sh
Use this skill when evaluating or installing a skill from skills.sh. Treat skills.sh as an external marketplace: verify ownership, official status, audits, maintenance signals, and local security implications before recommending any install command.
Owner: pcorazao_uhg
Super-Linter Configuration Generator
Generate and configure GitHub Super-Linter setup including workflow files, environment configuration, and pre-commit hooks for new or existing repositories.
Owner: epic-platform-sre
Harmony Setup
Setup guide for creating new projects with the Harmony Design System, including license keys, Node.js prerequisites, Artifactory NPM configuration, and React integration.
Owner: pcorazao
cave-man
Terse technical response style that removes filler while preserving substance
Owner: epic-platform-sre
claude-sync
Sync Codex settings to Claude Code — converts model, plugins, env vars, and trust level to ~/.claude/settings.json
Owner: epic-platform-sre
drzero-ping
Health check for the DrZero Codex plugin, shared config, custom agents, support scripts, and scoring runtime
Owner: epic-platform-sre

