1.1K skills · sorted by relevance
Check estimated token usage against daily limits before and after each automated loop run. Switch to reporting only, exit early when required, and record run outcomes so repeated agent work stays within configured limits.
Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.
Compare two GEO audits, which assess a site's readiness for AI search visibility, and produce a monthly client report. Summarize score changes, crawler access, completed actions, newly discovered issues, and priorities for the following month.
Add Sentry error reporting and performance monitoring to services, scheduled jobs, and database operations. Follow examples for capturing exceptions with useful context and measuring execution time through spans, which record individual operations for investigation.
Verify work before reporting completion, committing changes, or creating a pull request. Run the checks that support each claim, inspect their output and exit codes, and report the actual results rather than relying on assumptions or agent reports.
Verify development results before reporting success or preparing commits and pull requests. Run checks that support each claim, inspect their actual output, and report remaining gaps instead of relying on assumptions or another agent’s success message.
Create or modify Excel workbooks, then independently check the saved file with Python. Verify required sheets, columns, populated cells, row counts, and sample selections against the requested structure before reporting the work as complete.
Check generated PDFs with PyPDF2 before reporting completion. A Python script verifies that each file can be opened and has the expected page count, helping identify outputs that need regeneration.
Organize authorized phishing exercises from sending infrastructure and email scenarios to landing pages and reporting. Uses GoPhish campaign tracking to review opens, clicks, and submissions while assessing employee awareness and email security controls.
Turn penetration test and red team results into reports for executives and technical teams. Structure findings, explain severity scores and business impact, organize evidence, and document remediation steps and retest plans.
Organize red team exercises that simulate adversaries to assess an organization's detection and response. Covers engagement rules, infrastructure, operational controls, evidence handling, and reports that help security teams review gaps and prioritize improvements.
Trace a security finding from an attacker’s entry point to its impact using repository evidence. Examine access, permissions, existing defenses, and counterevidence to assess severity and decide whether the finding warrants reporting.
Connect AI agents to Mission Control through its API to register agents, retrieve assigned tasks, report progress, manage skills, and check agent or system status from scripts and automated workflows.
Use concrete JSON and Markdown examples to structure Sergo tool caches, strategy histories, improvement tasks, and reports. The templates show which fields to record and how to organize findings for review.
Guide bug bounty work from target research and vulnerability hunting through validation and reporting. Compare authenticated users, investigate related weaknesses, and organize reproducible evidence of practical impact before preparing a submission.
Plan bug bounty sessions around a clear goal and selected vulnerability types. Guides movement through reconnaissance, mapping, discovery, proof, and reporting, with prompts and routing to help decide what to investigate next.
Verify OpenMausBot server and conversation changes in an isolated instance using a fake engine, a stand-in for the real engine. Follow the canonical verification guide and shared control tool to check supported server workflows before reporting success.
Prepare Bugcrowd submissions with accurate vulnerability categories, evidence-based severity requests, and explanations of program scope. Structure references between related reports, document QA testing conditions, and draft responses when a finding is downgraded or considered out of scope.
Guide bug bounty work from asset discovery to validation and reporting, while resolving local locations of security tools, wordlists, and cloned projects. It covers web and AI security testing with an emphasis on demonstrated impact.
Estimate policy effects by constructing a weighted comparison from untreated regions or other units. Guides donor selection, weight fitting, placebo tests, and reporting, with examples in R, Python, and Stata for studies with few treated units.
Apply machine learning methods to estimate intervention effects and explore how effects vary across groups. Provides implementation examples, diagnostic checks, and reporting guidance for Double Machine Learning, causal forests, and variable selection.
Estimate how an intervention affects outcomes using Bayesian causal analysis. The workflow confirms causal assumptions with the user, selects a suitable method, checks whether findings withstand challenges, and reports effects with uncertainty and limitations.
Verify work before reporting it as complete by running fresh checks and reading their results. Match each claim to evidence, including test output, build results, bug reproduction, code changes, and requirement checks.
Review scientific manuscripts and grant proposals using structured checklists. Assess methods, statistics, reproducibility, ethics, and reporting completeness, then organize findings into a balanced report with major concerns, minor comments, and specific suggestions for revision.