2.7K skills · sorted by relevance
Plan authorized voice phishing assessments to evaluate how employees verify callers and report suspicious calls. Organize approved scenarios, record assessment outcomes, and summarize disclosure, verification, and reporting rates to review security awareness training.
Analyze suspicious Linux ELF executables through file inspection, runtime tracing, and reverse engineering. Identify malware behavior, network destinations, and persistence mechanisms, then organize findings and indicators for investigations involving servers, containers, or cloud infrastructure.
Improve resumes for software engineering, technical product management, data, and DevOps roles. Organize technical skills, connect achievements to business results, and highlight projects in a format suited to applicant tracking systems, software used to process job applications, and recruiters.
Approach engineering problems by checking assumptions, defining performance constraints, and choosing suitable tools before implementation. The skill guides algorithm analysis, complete code, performance optimization, and correctness checks through tests, assertions, or formal verification, meaning mathematical checks of correctness.
Draft weekly or monthly progress updates, launch announcements, and risk escalations for specific audiences. Turn shared project information into concise leadership summaries, detailed engineering updates, or customer-facing messages with clear next steps.
Create roadmap updates, release notes, and feature announcements tailored to executives, engineering teams, or customers. Choose a suitable roadmap format and generate changelogs from Git history, making progress, user value, dependencies, and next actions clear.
Plan controlled failure experiments to uncover system weaknesses. Define normal operating metrics, estimate affected users and reliability risk, set abort and recovery conditions, and turn experiment results into a structured review with follow-up actions.
Reviews code changes through documented engineering and product principles associated with named practitioners. Combines two engineering perspectives and one product perspective to produce findings with severity, attribution confidence, and technical reasoning for architecture, performance, or user experience issues.
Review engineering delivery plans, hiring proposals, and team changes through six operational questions. Assess delivery metrics, recruitment stages, management structure, and production practices, then produce a verdict and three concrete actions to address the findings.
Review proposal responses for missing requirements, compare competing products, and plan proof-of-concept trials that test customer needs. Supports technical sales work from requirement discovery and demo preparation through evaluation scorecards and technical proposals.
Evaluate whether Google SecOps rules detect threats described in articles or supplied text. Generate simulated attack logs, identify coverage gaps, summarize matching rules, and create rules for uncovered threats, with user approval before adding them.
Review unresolved Plain support tickets for missed response or resolution deadlines, VIP accounts, and serious problems. Route qualifying tickets to the responsible team, create linked Linear issues for engineering work, and post internal Slack alerts.
Use a structured starting point to write new context engineering skills. Organize activation conditions, responsibilities, practical steps, examples, and common mistakes, while keeping detailed references separate and clarifying boundaries with related skills.
Create slides for internal engineering talks or conference presentations using a dark color scheme and a monospaced font. Organize the deck around an agenda, code examples, key points, terminal screenshots, and a closing Q&A.
Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.
Diagnose why an AI workflow becomes inconsistent despite receiving extensive information. Through guided questions, define what to retain, retrieve when needed, or exclude, and develop a memory structure and a research-to-implementation process with focused context.
Execute software engineer specializing in creating production-ready ADK agents with best practices, code structure, testing, and deployment automation. Use when asked to "build ADK agent", "create agent code", or "engineer ADK application". Trigger with relevant phrases based on skill purpose.
The English summary is being prepared. Showing the original description.
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
The English summary is being prepared. Showing the original description.
Write, review, and improve blog posts for the Sentry engineering blog following Sentry's specific writing standards, voice, and quality bar. Use this skill whenever someone asks to write a blog post, draft a technical article, review blog content, improve a draft, write a product announcement, create an engineering deep-dive, or produce any written content destined for the Sentry blog or developer audience. Also trigger when the user mentions "blog post," "blog draft," "write-up," "announcement post," "engineering post," "deep dive," "postmortem," or asks for help with technical writing for Sentry. Even if the user just says "help me write about [feature/topic]" — if it sounds like it could become a Sentry blog post, use this skill.
The English summary is being prepared. Showing the original description.
Prompt engineering and LLM evaluation. Use when optimizing prompts, designing prompt templates, evaluating LLM outputs, building agentic systems, implementing RAG, creating few- shot examples, or designing structured-output workflows.
The English summary is being prepared. Showing the original description.
Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.
The English summary is being prepared. Showing the original description.
VP of Engineering advisor on org design, productivity, quality, delivery, and capacity planning. Use when scoring engineering org health, designing the eng org, planning capacity, or building the productivity dashboard.
The English summary is being prepared. Showing the original description.
Analytics engineering across data modeling, dbt, transformation, and semantic layers. Use when building dbt models, designing star schemas, writing staging or mart SQL, configuring data tests, or optimizing warehouse queries.
The English summary is being prepared. Showing the original description.
Analyzes RFP responses for coverage gaps, builds competitive feature matrices, and plans proof-of-concept engagements for pre-sales engineering
The English summary is being prepared. Showing the original description.