All authors
Claude Skills by Dadmin88
github.com/Dadmin88818 skills21 installs1,070 views
- Campaign Asset ProductionProduce a coherent family of campaign/social assets across formats while preserving concept, hierarchy, brand recognition, and content-safe adaptation.Votes: 0GitHub stars: 16
- Diagram Visual DesignDesign explanatory diagrams that clarify relationships, flow, hierarchy, architecture, or process using restrained visual encoding and accurate labels.Votes: 0GitHub stars: 16
- Graphic CompositionCreate a 2D communication graphic from hierarchy, grid, typography, imagery, whitespace, focal path, and channel constraints.Votes: 0GitHub stars: 16
- Presentation Visual SystemCreate a reusable presentation visual system covering grid, title/body hierarchy, charts/diagrams, imagery, callouts, section transitions, and dense-content patterns.Votes: 0GitHub stars: 16
- Production Export PreflightPreflight and export graphic assets for digital or print delivery with correct dimensions, resolution, color mode/profile, bleed/safe areas, fonts, transparency, compression, naming, and source preservation.Votes: 0GitHub stars: 16
- Acquisition FunnelDesign and analyze an acquisition funnel from audience exposure through qualified visit, lead or signup, activation, and downstream value with channel economics and quality safeguards.Votes: 0GitHub stars: 16
- Activation ExperimentDesign a growth experiment intended to improve activation using one explicit behavioral hypothesis, stable exposure, product-value metrics, segment analysis, and retention guardrails.Votes: 0GitHub stars: 16
- Channel TestTest a growth channel with a bounded audience, offer, creative, landing path, spend or effort budget, tracking, downstream quality measure, and explicit scale or stop criteria.Votes: 0GitHub stars: 16
- Growth ExperimentDesign a growth experiment with a clear bottleneck, hypothesis, intervention, metric, guardrails, and learning plan.Votes: 0GitHub stars: 16
- Retention AnalysisAnalyze retention from a meaningful cohort and repeated-value definition, separating lifecycle, segment, acquisition quality, product change, seasonality, and resurrection effects.Votes: 0GitHub stars: 16
- Bulk Config RolloutApply an approved Hermes configuration or provider setup plan across enumerated profiles in bounded, verifiable batches.Votes: 0GitHub stars: 16
- Config Verification And RollbackVerify effective Hermes configuration after rollout, detect drift or partial application, and restore approved prior values safely.Votes: 0GitHub stars: 16
- Hermes Config InventoryInventory installed Hermes profiles, configuration scope, effective values, provider status, and authoritative selection metadata without changing state.Votes: 0GitHub stars: 16
- Profile Selection And Change PlanResolve profile criteria and requested Hermes settings into an exact, user-approved dry-run matrix with exceptions, risks, and rollback values.Votes: 0GitHub stars: 16
- Capacity PlanningPlan infrastructure capacity from measured demand, resource bottlenecks, growth, failure headroom, burst behavior, scaling latency, quotas, and overload policy.Votes: 0GitHub stars: 16
- Disaster RecoveryDesign and validate disaster recovery around business recovery objectives, durable data, dependency restoration, rebuildability, access, runbooks, and tested recovery evidence.Votes: 0GitHub stars: 16
- Infrastructure ChangePlan and execute an infrastructure change with current-state discovery, blast-radius control, reproducibility, observability, validation, and recovery.Votes: 0GitHub stars: 16
- Infrastructure DesignDesign runtime infrastructure around service requirements, failure domains, identity, networking, storage, capacity, operability, reproducibility, and controlled evolution.Votes: 0GitHub stars: 16
- NetworkingDesign, change, or diagnose infrastructure networking from explicit traffic flows through naming, routing, filtering, encryption, discovery, load balancing, and path validation.Votes: 0GitHub stars: 16
- ObservabilityDesign infrastructure observability that answers operational questions across compute, network, storage, runtime, dependencies, saturation, failures, and recovery without collecting noise for its own sake.Votes: 0GitHub stars: 16
- Runtime DebuggingDiagnose infrastructure/runtime failures by tracing evidence across process, container, host, network, storage, resource pressure, configuration, dependency, and deployment layers.Votes: 0GitHub stars: 16
- Contract TestingTest an integration boundary against explicit request, response, event, schema, error, authentication, pagination, and compatibility contracts without confusing mocks with provider truth.Votes: 0GitHub stars: 16
- External Api IntegrationIntegrate an external API through authoritative contract discovery, typed mapping, authentication, pagination, limits, compatibility, resilient client behavior, and provider-isolated application boundaries.Votes: 0GitHub stars: 16
- External IntegrationImplement a robust external-system integration with contract discovery, authentication, mapping, idempotency, rate limits, retries, observability, and failure isolation.Votes: 0GitHub stars: 16
- Integration DebuggingDiagnose cross-system integration failures by reconstructing one operation across internal mapping, authentication, network, provider request/response, retries, asynchronous callbacks, persisted state, and reconciliation.Votes: 0GitHub stars: 16
- Oauth IntegrationIntegrate a standards-based OAuth or OpenID Connect provider using the provider-supported flow, explicit scopes, identity mapping, credential lifecycle, compatibility, and negative-path validation.Votes: 0GitHub stars: 16
- Retry IdempotencyDesign integration retries and idempotency so timeouts, duplicate delivery, uncertain outcomes, rate limits, and replay cannot silently duplicate or lose external side effects.Votes: 0GitHub stars: 16
- Webhook DesignDesign inbound or outbound webhooks with authenticated origin, stable event contracts, fast acknowledgement, duplicate/reorder handling, retries, idempotent processing, observability, and replay recovery.Votes: 0GitHub stars: 16
- Content LifecycleManage knowledge content from proposal through authoring, review, publication, revision, validation, archival, and removal using ownership, freshness signals, source changes, and reader evidence.Votes: 0GitHub stars: 16
- Knowledge Base DesignDesign an internal or customer knowledge base around audiences, recurring questions, source authority, article types, navigation, search, ownership, permissions, freshness, and feedback loops.Votes: 0GitHub stars: 16
- Knowledge CurationTurn scattered information into a maintained knowledge asset with clear scope, sources, ownership, discoverability, and freshness rules.Votes: 0GitHub stars: 16
- Knowledge Gap AnalysisIdentify missing or weak organizational knowledge by comparing recurring questions, support and incident demand, search failures, process dependency, source coverage, and decision risk against existing trusted content.Votes: 0GitHub stars: 16
- Source Of Truth AuditAudit organizational sources of truth by identifying authoritative systems, duplicated facts, conflicting records, ownership, freshness, synchronization, access, and downstream consumers.Votes: 0GitHub stars: 16
- TaxonomyDesign and maintain a knowledge taxonomy of concepts, terms, categories, relationships, synonyms, and ownership so information remains findable without forcing one rigid hierarchy onto every use case.Votes: 0GitHub stars: 16
- Cross Functional ChecklistBuild a launch checklist that coordinates cross-functional dependencies, evidence, owners, timing, sequencing, and handoffs without turning every launch into the same template.Votes: 0GitHub stars: 16
- Go Live CommunicationsCoordinate launch-window communications so internal teams, users, customers, partners, support, and operators receive the right message, timing, action, and source of truth for their role.Votes: 0GitHub stars: 16
- Launch PlanCoordinate a launch across product readiness, messaging, channels, support, documentation, analytics, timing, owners, and contingency plans.Votes: 0GitHub stars: 16
- Launch RiskBuild and maintain a launch-specific risk view covering failure scenarios, probability, impact, detectability, prevention, contingency, decision triggers, and accountable owners.Votes: 0GitHub stars: 16
- Readiness CheckAssess launch readiness across product behavior, quality, operations, support, communications, dependencies, legal or compliance, analytics, rollback, and owner sign-off using evidence rather than optimistic status.Votes: 0GitHub stars: 16
- Contract IntakeIntake a contract or commercial agreement by capturing parties, purpose, scope, dates, value, data or security implications, business owner, requested decision, dependencies, and review status for qualified legal handling.Votes: 0GitHub stars: 16
- Counsel HandoffHand a legal matter to qualified counsel with complete factual context, authoritative documents, timeline, business objective, decisions required, deadlines, prior guidance, and clearly separated assumptions.Votes: 0GitHub stars: 16
- Legal Ops IntakeStructure a legal or policy operations request into facts, documents, deadlines, jurisdictions, decisions needed, and escalation points for qualified review.Votes: 0GitHub stars: 16
- Legal Request TriageTriage incoming legal or legal-adjacent requests by issue type, urgency, jurisdiction or contract context, factual completeness, business impact, deadlines, confidentiality, and the qualified owner needed for interpretation.Votes: 0GitHub stars: 16
- Obligation TrackingTrack contractual or legal-process obligations by source clause or decision, owner, action, due date, recurrence, evidence, status, dependency, and escalation without independently interpreting ambiguous legal requirements.Votes: 0GitHub stars: 16
- Policy RecordMaintain an authoritative organizational policy record with owner, scope, approval, effective date, version, requirements, exceptions, related procedures, evidence, review cycle, and supersession history.Votes: 0GitHub stars: 16
- Encounter DesignDesign gameplay encounters by combining player abilities, enemies or hazards, space, objectives, resources, information, escalation, failure, and replay variation.Votes: 0GitHub stars: 16
- Level DesignDesign a playable level around goals, pacing, routes, affordances, challenge, teaching, landmarks, metrics, and playtest evidence.Votes: 0GitHub stars: 16
- Level FlowDesign and evaluate player flow through spaces using goals, orientation, choice, gating, traversal, landmarks, backtracking, recovery, and pacing.Votes: 0GitHub stars: 16
- PacingShape the rhythm of challenge, traversal, discovery, narrative, rest, resource pressure, and intensity across a level using timed play and player-state evidence.Votes: 0GitHub stars: 16
- Playtest IterationTurn level playtest observation into prioritized spatial, encounter, signposting, pacing, and balance changes without designing by anecdote.Votes: 0GitHub stars: 16