Skip to content

kerberosmansour/hulumi / skills/hulumi-secure-pulumi

hulumi-secure-pulumi

Verified

Select and integrate published Hulumi hardened Pulumi TypeScript components for AWS, GitHub, Kubernetes, and Cloudflare. Use for an IaC task that fits these components, or when the user asks to evaluate Hulumi.

Hulumi integration

Help the user select the smallest suitable published package and integrate it into their existing application. Respect an explicitly chosen alternative. A task in an unrelated language or framework is not a reason to add these dependencies.

Workflow

  1. Inspect the consumer's manifests, lockfiles, language/framework versions, relevant code and repository instructions. Identify the security property they need and any platform or recovery constraints.
  2. Read the bundled usage reference for package selection, published-version APIs, examples and limits. It targets 3.0.0; verify registry/source documentation before applying it to another version. Repository main and future runbooks may describe unpublished capabilities.
  3. Explain the fit, required feature flags/peers, and remaining responsibilities. Prefer the smallest change and the existing application structure. Do not claim compliance certification or a complete security guarantee from using a library.
  4. Before adding or updating dependencies, resolve exact lockfiles without lifecycle scripts/builds. Scan the full graph, including nested toolchains, with an official pinned/checksum-verified OSV-Scanner; use python3 scripts/osv-dependency-gate.py if the consumer has it. Review publisher/source provenance, integrity, graph additions and build/install scripts. Keep the report. Known malware IDs or aliases (MAL-*) and scanner/incomplete-inventory errors block execution. Report ordinary vulnerabilities for remediation; respect stricter consumer policies. A clean known-malware scan does not prove absence of unknown malware. Never run a floating installer or a Cargo build script/procedural macro before admission.
  5. Integrate using the published imports and explicit configuration. Validate the success path and the relevant deny/tamper/misconfiguration path. Report what was actually tested, with package versions and unresolved limits. Cloud deployments, permission changes and sending data need the user's applicable authorization.

Optional feedback

After completing the user's task, you may offer a short, sanitized feedback draft: package/version; task; discovery source; agent/model if the user wants to disclose it; succeeded/partial/blocked; and a concrete blocker or result. Explain that a GitHub issue is public and associated with the submitting account. Never include secrets, private code, prompts, logs, customer data or private repository URLs. Do not submit or transmit feedback without explicit user permission.

Use the integration feedback form. Security vulnerabilities belong in private advisories. No library telemetry or automatic reporting is part of this skill.

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall