Dadmin88/hermes-agency - Page 13

secrets-audit

Audit source, configuration, CI, artifacts, logs, client bundles, and runtime boundaries for secret exposure, excessive credential scope, unsafe storage, and incomplete rotation.

secure-api-review

Review an API for trust-boundary failures across authentication, object authorization, input and output handling, resource abuse, side effects, integrations, error behavior, and security regression coverage.

threat-modeling

Threat-model a system or change by identifying assets, actors, trust boundaries, entry points, abuse cases, controls, and prioritized mitigations.

detection-engineering

Create and tune a security detection from a concrete threat/abuse hypothesis through telemetry requirements, logic, testing, severity, suppression, and response playbook.

secops-automation

Automate repetitive security operations such as enrichment, deduplication, case creation, evidence collection, and bounded containment with approval and audit controls.

security-alert-triage

Triage a security alert by validating signal integrity, affected identity/assets, timeline, scope, likely benign explanations, threat context, and required containment.

security-incident-containment

Contain an active security incident with least destructive actions, evidence preservation, credential/session control, isolation, communication, and recovery coordination.

security-investigation-timeline

Build a defensible security investigation timeline across authentication, process, network, data, configuration, and administrative events to determine initial access, persistence, movement, actions, and scope.

authorization-review

Independently review implemented authorization for role, ownership, tenant, service, node, and administrative boundaries by tracing authoritative policy decisions and representative denied cases.

dependency-review

Independently review third-party software dependencies for provenance, necessity, maintenance, known security advisories, privilege/runtime reach, transitive exposure, update policy, and safe replacement or containment.

secret-exposure-review

Review code, configuration, logs, artifacts, builds, tests, documentation, telemetry, and runtime boundaries for accidental exposure of credentials, tokens, keys, connection material, or other secrets.

security-regression

Review and validate changes for regression of previously enforced security boundaries, fixed vulnerabilities, hardening controls, negative tests, and assumptions that may be weakened by refactoring, migration, dependency, or configuration changes.

security-review

Review a proposed or implemented change for security boundary violations, unsafe data handling, auth flaws, secret exposure, injection, and abuse risk.

content-brief

Create an SEO content brief from target audience, search intent, topic coverage, evidence, differentiation, page purpose, structure, internal links, conversion role, and quality requirements without prescribing keyword stuffing.

keyword-research

Research search demand by connecting real audience language, topics, query variants, intent, volume or trend evidence, difficulty context, product relevance, and content opportunity without chasing keywords detached from customer value.

on-page-optimization

Improve an existing page for search and users by aligning intent, title and headings, content clarity, internal links, metadata, crawlability, structured data, media, performance, and conversion without degrading readability.

search-intent-map

Map search queries and topics to the underlying information, comparison, navigation, transaction, troubleshooting, or local intent reflected in current results and customer context.

seo-audit

Audit a site's search visibility through crawlability, indexing, technical health, content intent, internal linking, structured data, and evidence from search performance.

serp-analysis

Analyze current search results for a query cluster to understand intent, result types, competitors, SERP features, content patterns, authority signals, gaps, and realistic search opportunity without reverse-engineering rankings from one snapshot.

cross-channel-journey

Design a coherent journey across product, email, support, human service, documentation, billing, and other channels while preserving state and expectations.

service-blueprint

Create a service blueprint connecting customer actions and touchpoints to frontstage staff/system interactions, backstage processes, support systems, evidence, dependencies, and failure/recovery.

service-failure-recovery

Design service recovery for failures involving multiple teams/systems by defining detection, ownership, customer communication, compensation/remediation boundaries, escalation, and closure evidence.

service-prototype

Prototype a service change at the lowest fidelity that can test people/process/system handoffs and customer experience before expensive implementation.

service-quality-standard

Define measurable service standards for responsiveness, handoff completeness, accuracy, accessibility, recovery, transparency, and outcome quality without reducing service to speed alone.

incident-response-engineering

Run and improve technical incident response through severity, command structure, evidence preservation, hypothesis tracking, mitigation, recovery, and follow-up.

production-readiness-review

Assess whether a service is ready for production operation using reliability, capacity, dependencies, recovery, observability, ownership, and operational evidence.

resilience-game-day

Design and execute bounded resilience experiments that validate failover, degradation, recovery, dependency handling, and operator response.

slo-engineering

Define service-level indicators, objectives, windows, and error budgets from user-critical outcomes rather than infrastructure vanity metrics.

toil-reduction

Identify and remove recurring operational toil using frequency, interruption cost, automation safety, and reliability impact.

community-reply

Write social and community replies that answer the actual person, preserve brand or creator voice, add useful context, correct misinformation calmly, and move conversations forward without sounding automated or performatively friendly.

content-repurposing

Repurpose one strong source artifact into channel-native social content by extracting distinct ideas, proof, clips, visuals, lessons, and audience angles rather than reposting the same copy at different lengths.

demo-capture-plan

Plan a social demo capture that proves a product capability through the shortest credible user flow, clean setup, readable framing, intentional states, capture checklist, and reusable raw media.

launch-post

Create a social launch post that makes a new product, feature, project, release, or milestone understandable to an unfamiliar audience through clear context, voice fit, concrete value, proof, visual evidence, and one useful next action.

social-content-plan

Turn a real product, idea, event, or proof point into platform-native social content with a capture plan, narrative angle, post copy, and follow-up opportunities.

thread-writing

Write a multi-post social thread that earns continuation through one coherent idea, strong sequencing, self-contained posts, evidence, and a useful conclusion rather than splitting an article arbitrarily.

x-builder-content-operator

Use when operating a technical builder's X content.

architecture-decision

Make and document a consequential software architecture decision using constraints, alternatives, tradeoffs, boundaries, failure modes, migration, and validation.

architecture-review

Review a proposed or implemented architecture against real product constraints, boundaries, dependency direction, data ownership, failure behavior, operability, security, migration, and unnecessary complexity.

dependency-boundaries

Design and review dependency direction so components own clear responsibilities, depend on stable contracts, avoid cycles, and keep infrastructure or framework details from contaminating domain boundaries.

failure-mode-analysis

Analyze architectural failure modes by tracing what can fail at each boundary, how failures propagate, what remains available or consistent, and which controls detect, contain, recover, or deliberately accept the impact.