All categories
DevOps & Cloud
Deployment, cloud, containers, CI/CD, monitoring, and infrastructure
- 20,288
- 846
Security grades appear on each card once the skill has been scanned. Newly imported skills may briefly show without a grade until the backfill job runs.
Open in full browserBrowse devops & cloud skills
Showing 6,865–6,888 of 20,288 skills
- Technology ArchitectEvaluates and standardizes technology stack and platforms using industry frameworksVotes: 0GitHub stars: 2
- Solution ArchitectDesigns specific solutions and integration patterns using cloud architecture frameworksVotes: 0GitHub stars: 2
- Governance SpecialistEstablishes architecture governance and decision frameworks using COBIT and ISO standardsVotes: 0GitHub stars: 2
- Devops AutomatorSets up CI/CD, infrastructure as code, and deployment pipelines for automated deliveryVotes: 0GitHub stars: 2
- Launch Product> Domain: ceo-automation/launch-product | Office: CPO/CTO > Reference: `ceo-automation-prompts.md` lines 1972-2128Votes: 0GitHub stars: 2
- Draft Intercreditor AgreementDraft an intercreditor agreement governing the relationship between first-lien and second-lien lenders, addressing standstill mechanics, automatic lien release scope, adequate protection waivers, refinancing treatment, amendment consent rights, and consistency of defined terms across related financing documents.Votes: 0GitHub stars: 57
- Draft Source Code Escrow AgreementDraft a beneficiary-oriented source code escrow agreement and a negotiation issues memo for a software-as-a-service license transaction, using the escrow agent's template and the deal documents as inputs.Votes: 0GitHub stars: 57
- Draft Closing Checklist MemorandumClosing checklist memorandum for an intellectual property and technology asset purchase transaction, organizing pre-closing conditions, closing deliverables, and post-closing obligations derived from the governing transaction documents.Votes: 0GitHub stars: 57
- Extract Post Closing ObligationsGuides systematic extraction of post-closing obligations from a stock purchase agreement and related transaction documents into a compliance tracker, with cross-document consistency review.Votes: 0GitHub stars: 57
- Summarize State Ai Governance Bill For Product And Engineering TeamsAgents summarize the bill's substantive requirements for product and engineering leadership, identifying implementation ambiguities, potential conflicts between documentation/retention requirements and privacy obligations, and opportunities to seek regulatory guidance on unresolved interpretive questions.Votes: 0GitHub stars: 57
- Map Eu Ai Act Transparency Obligations To Existing Product DocumentationAgents produce a general EU AI Act overview by classifying the product under the relevant high-risk categories, identifying the applicable conformity assessment pathway, checking whether any existing risk assessment is adequate for AI-specific risk management, noting the EU database registration requirement, and addressing the practical tension between trade secret protection and mandatory transparency obligations.Votes: 0GitHub stars: 57
- Draft Updated Code Of ConductAgents address the main substantive code topics but omit specific off-channel communications policy requirements arising from a government enforcement context, phase-specific compliance deadlines for supply chain due diligence directives, employee monitoring consultation requirements in jurisdictions with co-determination rights, and the correct scope of clawback coverage linked to applicable securities law.Votes: 0GitHub stars: 57
- Draft Board Resolution Credit FacilityBoard resolution authorizing entry into a senior secured revolving credit facility, with a cover memorandum identifying observer-versus-director classification issues, signing authority gaps, stockholder consent requirements, and financial covenant discrepancies.Votes: 0GitHub stars: 57
- Scenario 02Ensures a notice of arbitration treats service availability and data-loss allegations as distinct claims, states an accurate incident timeline, includes the governing law, and references the filing fee.Votes: 0GitHub stars: 57
- Zod Error Handling> Handle Zod validation failures with safeParse, ZodError, error.format, error.flatten, and custom error mapsVotes: 0GitHub stars: 20
- Vue Teleport Pattern> Render a component's HTML at a different location in the DOM using Vue's TeleportVotes: 0GitHub stars: 20
- Svelte Adapter Config> Deploy SvelteKit to any platform by selecting and configuring the correct adapter in svelte.config.jsVotes: 0GitHub stars: 20
- Security Secrets Lifecycle> Secrets are born (generated), distributed (delivered to consumers), rotated (replaced on > schedule), and die (revoked and destroyed) -- manage every phase or the secret manages youVotes: 0GitHub stars: 20
- Security Sbom Provenance> Know exactly what is in your software (SBOM) and prove how it was built (provenance) -- because > you cannot secure what you cannot inventoryVotes: 0GitHub stars: 20
- Security Post Incident Review> Organizations that conduct blameless post-incident reviews after every significant security > incident reduce their recurrence rate by identifying systemic weaknesses; organizations that > skip the review are condemned to repeat the same failures with different symptomsVotes: 0GitHub stars: 20
- Security Log Correlation> Correlate events across multiple log sources to detect attacks that are invisible in any > single log stream -- because attackers do not confine their activities to one systemVotes: 0GitHub stars: 20
- Security Forensics Fundamentals> Digital forensics is the discipline of collecting, preserving, and analyzing evidence from > compromised systems -- done correctly, it reveals the full attack narrative; done poorly, it > destroys the evidence needed to understand what happened and prevent recurrenceVotes: 0GitHub stars: 20
- Security Environment Variable Risks> Environment variables are visible in process listings, inherited by child processes, > captured in crash dumps, and logged by every debugging tool -- they are the worst place > to store secretsVotes: 0GitHub stars: 20
- Security Craft> LLM-judgment critique of security posture for TS/JS source — the ceiling counterpart to `harness-security-scan` (CVE/OWASP rule-based floor) and `harness-security-reviewer` (procedural review). Threat-modeling-as-skill rather than pattern-matching. Critiques whether trust boundaries are respected, where implicit privilege escalation lurks, whether the code defends in depth or just at the gate, whether principle of least authority is honored. Sixth non-design member of the craft-pipeline ini...Votes: 0GitHub stars: 20