williamlimasilva/github-codespaces-efficiency
skills/github-codespaces-efficiency/SKILL.md
Audit and improve GitHub Codespaces efficiency. Use this skill when a user wants faster Codespaces startup, lower Codespaces spend, slim devcontainers, right-size machines, tune idle timeout, or scope prebuilds to branches with sustained usage.
development
Updated May 26, 2026
$ install --global
skillsauthnpx skillsauth add williamlimasilva/.copilot github-codespaces-efficiencyInstall 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: May 26, 2026, 2:09 AM36.3s3 files scanned
SKILL.md
- name:
- github-codespaces-efficiency
- description:
- Audit and improve GitHub Codespaces efficiency. Use this skill when a user wants faster Codespaces startup, lower Codespaces spend, slim devcontainers, right-size machines, tune idle timeout, or scope prebuilds to branches with sustained usage.
GitHub Codespaces Efficiency
Use this skill as a lean entrypoint for GitHub Codespaces efficiency work. Inspect the repo, identify waste, and load only needed references.
If no .devcontainer/ exists yet, load references/codespaces.md and define a baseline before proceeding with the steps below.
Use This Skill When
- The user wants faster Codespaces startup or lower Codespaces spend.
- The repo has a
.devcontainer/or explicit Codespaces configuration questions. - The user asks for devcontainer optimization, machine sizing, prebuild strategy, or idle-timeout guidance.
- The user is setting up Codespaces for the first time or needs help creating a new
.devcontainer/from scratch.
Load Only What You Need
references/codespaces.md— devcontainer, machine-sizing, prebuild, idle-timeout guidance, and reporting.references/review-rubric.md— load only for review passes.
Core Workflow
1. Measure first
find .devcontainer -maxdepth 2 -type f
gh codespace list
repo=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
gh api "/repos/$repo/codespaces/machines"
If gh auth fails or the user lacks repo admin scope, proceed with static analysis of .devcontainer/ files; mark machine-type and prebuild recommendations as unverified.
Look for: devcontainer image >2 GB or more than 10 features, machine type larger than usage data supports, missing devcontainer-lock.json (recommend adding — many repos predate lock-file support), prebuilds scoped too broadly, and idle timeout mismatched to usage patterns.
2. Apply guardrails
Check each proposed fix against these rules before recommending it:
- Does not remove tools the team uses every day — drop any fix that strips required development tools or extensions.
- Does not assume smaller is always better — balance machine cost against developer experience and throughput.
- Does not turn the devcontainer into a production image — drop any fix that adds production-only dependencies unless the team explicitly requires it.
- Incremental changes preferred — a greenfield baseline is appropriate only when no
.devcontainer/exists; flag (do not drop) changes that restructure an existing config. - Repo changes stay separate from org settings — split any fix that mixes repo-editable files with org-level or user-level Codespaces settings into two distinct recommendations.
3. Select the top 3 fixes
From the six candidates below, keep only those supported by audit evidence from step 1 and passing all guardrails from step 2. Rank survivors by estimated monthly cost savings (USD). Select all candidates that meet both criteria, up to a maximum of 3.
- Trim devcontainer — remove features, packages, or extensions not needed for everyday development work; target image <2 GB and fewer than 10 features
- Right-size machine type — match to observed usage patterns; if data is unavailable, state assumptions explicitly
- Scope prebuilds — enable for the default branch,
release/*branches active in the last 14 days, and branches with more than 5 Codespaces per week; disable for all others - Tune idle timeout — 30 min default; 15 min if most sessions end before 30 min; 60 min if most sessions run longer
- Remove unused extensions or port-forwarding rules
- Reduce devcontainer image size and improve layer caching
4. Verify
- Start a test Codespace to confirm devcontainer changes build and start as expected.
- Validate machine sizing against observed usage when telemetry is available; otherwise mark as unverified.
- Treat unexpected build or startup failures as real bugs even when the configuration looks correct.
Required Output
Waste sources: [top cost or startup-time drivers]
Proposed fixes: [top 3 changes supported by audit evidence and passing guardrails]
Validation: [proven live / static-only / remaining risk]
Impact:
- Startup time: [expected] / [measured if available]
- Monthly spend: [expected] / [measured if available]
- Resource utilization: [expected] / [measured if available]
References
references/codespaces.mdreferences/review-rubric.md— load when reviewing completed efficiency work
Related Skills
williamlimasilva/workshop-create
tools
VerifiedTrustedCommunity
Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/vcpkg
development
VerifiedTrustedCommunity
Guide for setting up vcpkg in C++ projects, managing dependency versions, and cross-compiling. Covers manifest initialization, CMake and Visual Studio integration, classic-to-manifest migration, version pinning, baselines, overrides, triplets, and cross-compilation. Use when a user is working with vcpkg project setup, installation, version management, or cross-platform builds. For specialized tasks, additional references cover custom registries and overlay ports (references/registries.md), CI/CD and binary caching (references/ci.md), and troubleshooting and dependency lifecycle (references/troubleshooting.md).
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/signal-write
testing
VerifiedTrustedCommunity
Emit structured agent signals — hands-up, blocked, done, checkpoint, partnership. Signals are written as JSON to .signals/ for dashboard consumption and noted in the journal for persistence.
SKILL.mdUpdated Jul 22, 2026
williamlimasilva/markstream-install
development
VerifiedTrustedCommunity
Install and configure Markstream streaming Markdown renderers for Vue, React, Svelte, Angular, Nuxt, and Vue 2 applications. Use for package selection, minimal peer dependencies, CSS order, SSR boundaries, streaming mode, and renderer setup.
SKILL.mdUpdated Jul 22, 2026