
Claude Skills by Dadmin88
github.com/Dadmin88Integrate a standards-based OAuth or OpenID Connect provider using the provider-supported flow, explicit scopes, identity mapping, credential lifecycle, compatibility, and negative-path validation.
Design integration retries and idempotency so timeouts, duplicate delivery, uncertain outcomes, rate limits, and replay cannot silently duplicate or lose external side effects.
Design inbound or outbound webhooks with authenticated origin, stable event contracts, fast acknowledgement, duplicate/reorder handling, retries, idempotent processing, observability, and replay recovery.
MUST load first for Academy learning or go-learn requests.
Manage knowledge content from proposal through authoring, review, publication, revision, validation, archival, and removal using ownership, freshness signals, source changes, and reader evidence.
Design an internal or customer knowledge base around audiences, recurring questions, source authority, article types, navigation, search, ownership, permissions, freshness, and feedback loops.
Turn scattered information into a maintained knowledge asset with clear scope, sources, ownership, discoverability, and freshness rules.
Identify 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.
Audit organizational sources of truth by identifying authoritative systems, duplicated facts, conflicting records, ownership, freshness, synchronization, access, and downstream consumers.
Design 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.
MUST load first for Academy learning or go-learn requests.
Build a launch checklist that coordinates cross-functional dependencies, evidence, owners, timing, sequencing, and handoffs without turning every launch into the same template.
Coordinate 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.
Coordinate a launch across product readiness, messaging, channels, support, documentation, analytics, timing, owners, and contingency plans.
Build and maintain a launch-specific risk view covering failure scenarios, probability, impact, detectability, prevention, contingency, decision triggers, and accountable owners.
Assess 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.
MUST load first for Academy learning or go-learn requests.
Intake 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.
Hand a legal matter to qualified counsel with complete factual context, authoritative documents, timeline, business objective, decisions required, deadlines, prior guidance, and clearly separated assumptions.
Structure a legal or policy operations request into facts, documents, deadlines, jurisdictions, decisions needed, and escalation points for qualified review.
Triage 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.
Track 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.
Maintain an authoritative organizational policy record with owner, scope, approval, effective date, version, requirements, exceptions, related procedures, evidence, review cycle, and supersession history.
MUST load first for Academy learning or go-learn requests.
Design gameplay encounters by combining player abilities, enemies or hazards, space, objectives, resources, information, escalation, failure, and replay variation.
Design a playable level around goals, pacing, routes, affordances, challenge, teaching, landmarks, metrics, and playtest evidence.
Design and evaluate player flow through spaces using goals, orientation, choice, gating, traversal, landmarks, backtracking, recovery, and pacing.
Shape the rhythm of challenge, traversal, discovery, narrative, rest, resource pressure, and intensity across a level using timed play and player-state evidence.
Turn level playtest observation into prioritized spatial, encounter, signposting, pacing, and balance changes without designing by anecdote.
Create a low-cost playable blockout that proves scale, traversal, sightlines, routes, encounter spaces, gating, and camera behavior before art production.
MUST load first for Academy learning or go-learn requests.
Perform linguistic QA in rendered context for meaning, terminology, grammar, truncation, variables, directionality, formatting, cultural fit, and task completion.
Plan staged locale rollout using market/user need, translation capacity, product readiness, support/docs coverage, QA evidence, fallback, and ongoing maintenance ownership.
Prepare source product/content material for localization by removing ambiguous context, hard-coded assumptions, unsafe concatenation, and untranslatable constraints.
Build and maintain a multilingual terminology glossary with canonical source terms, definitions, context, approved translations, prohibited variants, and ownership.
Create a translation brief that supplies audience, tone, product context, screenshots, string relationships, variables, constraints, and escalation rules.
MUST load first for Academy learning or go-learn requests.
Review new narrative or lore content against established canon for chronology, geography, terminology, world rules, characters, factions, knowledge boundaries, and downstream consequences before it becomes authoritative.
Write faction lore that connects origin, ideology, internal tensions, leadership, resources, symbols, relationships, public reputation, secret knowledge, and historical change to established world canon.
Write item, object, equipment, artifact, or collectible descriptions that communicate function, world identity, ownership or history, tone, and discovery context within strict UI or inventory constraints.
Develop coherent world lore with causal history, cultures, institutions, beliefs, conflicts, and constraints that support stories and gameplay.
Write a concise canonical lore entry that records subject, time, place, relationships, significance, evidence or canon source, and unresolved questions without turning the knowledge base into narrative prose.
Review narrative material for continuity of chronology, character knowledge, motivation, relationships, injuries or resources, location, world rules, prior choices, and causal consequences across scenes or branches.
MUST load first for Academy learning or go-learn requests.
Map a market category by customer jobs, segments, solution types, substitutes, value chains, channels, business models, and boundaries so teams understand structure before choosing competitors or positioning.
Ground answers and documents in cited, verifiable sources.
Research what people actually say about any topic in the last 30 days. Pulls posts and engagement from Reddit, X, YouTube, TikTok, Hacker News, Polymarket, GitHub, and the web. Includes a doctor health check to diagnose broken or missing sources.
Research a market using current evidence on customers, categories, demand, pricing, trends, channels, and market structure.
Estimate market size using explicit market boundaries, customer or unit definitions, current evidence, top-down and bottom-up triangulation, adoption assumptions, and sensitivity ranges rather than false precision.
Research market pricing using current public and primary evidence on list price, packaging, discounts, usage metrics, willingness to pay, alternatives, switching cost, and perceived value.