dtsong

@dtsong source repo

171 skills
0 followers
7 hours ago last updated

▌
Bank Rec · dtsong bundle
Performs bank reconciliations between a bank statement export and GL cash detail. Use when the user provides a bank statement file (CSV, XLSX, or PDF) and a GL cash detail file and asks to reconcile, match transactions, identify outstanding items, or produce a bank rec workpaper. Outputs a matched/unmatched workbook, aged reconciling items, proposed adjusting JEs, and an evidence table.

0
installs
▌
Je Review · dtsong bundle
Reviews proposed journal entries for posting readiness. Use when the user provides a list or file of journal entries and asks to review, validate, check for errors, or approve for posting. Verifies debit/credit balance, account coding, support adequacy, memo quality, period appropriateness, duplicate risk, and unusual patterns. Classifies each entry as ready, needs clarification, or reject.

0
installs
▌
Firm Config · dtsong bundle
Loads firm-specific accounting configuration including chart of accounts, materiality thresholds, close calendar, approval matrix, and standard mappings. Use at the start of any workflow that needs to apply firm-specific rules rather than generic accounting conventions.

0
installs
▌
Pbc Package · dtsong bundle
Maps audit PBC request lists to support files, identifies gaps, drafts auditor responses, and assembles audit-ready evidence packages. Use when the user provides a PBC request list and a folder of support files and asks to match support to requests, identify missing items, flag duplicates or orphaned files, or draft responses to the auditor.

0
installs
▌
Flux Analysis · dtsong bundle
Performs month-end flux/variance analysis against prior period and budget. Use when the user provides a trial balance and asks to analyze variances, explain fluxes, produce variance commentary, or build a flux workpaper. Applies firm materiality thresholds, calculates dollar and percent changes, categorizes variance type, drafts explanations where support exists, and generates targeted preparer questions where it doesn't.

0
installs
▌
Prepaid Schedule · dtsong bundle
Builds and maintains prepaid expense amortization schedules. Use when the user provides vendor invoices, service period information, or an existing prepaid template and asks to extract prepaid items, build amortization schedules, calculate monthly expense, or generate journal entries for prepaid recognition and amortization. Produces a formula-driven schedule, not hardcoded tables.

0
installs
▌
Workpaper Standards · dtsong bundle
Use whenever producing an accounting workpaper, schedule, reconciliation, journal entry, or audit deliverable. Defines firm formatting conventions, the evidence-table requirement, journal entry templates, and the standard for source tie-outs. Required dependency for bank-rec, flux-analysis, prepaid-schedule, pbc-package, and je-review skills.

0
installs
▌
A11Y Audit · dtsong
Use when auditing accessibility compliance of a feature or codebase. Covers WCAG 2.2 AA conformance, screen reader compatibility, keyboard navigation, focus management, color contrast, reduced motion, and ARIA usage. Do not use for general UX review (use journey-mapping) or component interaction specs (use interaction-design).

0
installs
▌
I18N Review · dtsong
Use when reviewing internationalization readiness of a feature or codebase. Covers locale strategy, RTL layout, string externalization, pluralization, date/number formatting, and cultural UX adaptation. Do not use for general accessibility audits (use interaction-design).

0
installs
▌
Finance Tax Research · dtsong
Use when answering a federal, state, or international tax question that requires authoritative research. Covers IRC, Treasury Regs, Rev Rul/Proc, case law, and applicable treaty positions. Do not use for tax-provision computation (use finance-provision — Phase 3+).

0
installs
▌
E2e Testing · dtsong
Use when designing end-to-end test suites, visual regression testing, or cross-browser test strategies. Covers Playwright/Cypress test architecture, page object patterns, test data management, visual snapshot comparison, cross-browser matrix, and CI integration. Do not use for unit/integration test strategy (use testing-strategy) or code pattern audit (use pattern-analysis).

0
installs
▌
Finance Controls Audit · dtsong
Use when testing a SOX 404 control or designing a controls walkthrough. Covers control description, design effectiveness, operating effectiveness, deficiency evaluation, and remediation. Do not use for evidence-package preparation (use finance-evidence-package — Phase 3+).

0
installs
▌
Finance Reconciliation · dtsong
Use when reconciling a balance-sheet account during the close cycle. Covers sub-ledger to GL ties, intercompany eliminations, exception triage, and audit-ready documentation. Do not use for journal-entry construction (use finance-journal-entries) or close orchestration (use finance-close-checklist).

0
installs
▌
Schema Design · dtsong
Use when designing or modifying database schemas with migration plans. Covers entity definition, relationship mapping, normalization trade-offs, indexing strategies, and RLS policies. Do not use for API endpoint contracts (use api-design) or codebase analysis (use codebase-context).

0
installs
▌
Finance Close Checklist · dtsong
Use when orchestrating monthly or quarterly close. Covers the close calendar, sub-ledger cutoffs, accruals, reclass entries, and post-close review. Do not use for individual reconciliations (use finance-reconciliation) or journal-entry construction (use finance-journal-entries).

0
installs
▌
Finance Journal Entries · dtsong
Use when constructing a GAAP/IFRS journal entry from facts. Covers debit/credit selection, account coding, sub-ledger impact, and supporting memo. Do not use for reconciliation (use finance-reconciliation) or close orchestration (use finance-close-checklist).

0
installs
▌
Finops Analysis · dtsong
Use when analyzing cloud spending, cost attribution, or unit economics. Covers cost allocation tagging, reserved capacity planning, right-sizing, spot/preemptible usage, cost anomaly detection, and showback/chargeback models. Do not use for general infrastructure cost modeling (use cost-analysis) or deployment strategy (use deployment-plan).

0
installs
▌
Finance Variance Analysis · dtsong
Use when explaining actual-vs-plan or actual-vs-prior variance with commentary. Covers volume/price/mix decomposition, run-rate impact, and management commentary. Do not use for forecast revision (use finance-forecast-update — Phase 3+) or close orchestration (use finance-close-checklist).

0
installs
▌
Messaging Strategy · dtsong
Use when developing product messaging frameworks including value propositions, feature naming, microcopy guidelines, and CTA strategy. Covers voice and tone definition, conversion copy, and upgrade prompt language. Do not use for pricing architecture or paywall placement (use monetization-design) or onboarding funnels and referral systems (use growth-engineering).

0
installs
▌
Distributed Patterns · dtsong
Use when designing distributed systems or evaluating distributed architecture patterns. Covers CAP theorem trade-offs, consensus protocols (Raft, Paxos), saga orchestration, CRDTs, event sourcing, partition handling, distributed transactions, and failure detectors. Do not use for general API design (use api-design) or database schema design (use schema-design).

0
installs
▌
Enterprise Search Strategy · dtsong
Use when the council needs to surface organizational knowledge buried across multiple internal sources (wikis, design docs, ADRs, past tickets, postmortems, chat archives, code repos). Plans where to look, what to cross-reference, and how to synthesize findings into evidence the council can act on. Do not use for external market research (use competitive-analysis), library evaluation (use library-evaluation), or technology trend assessment (use technology-radar).

0
installs
▌
Mcs Change Control · dtsong bundle
Use when about to commit or merge in this repo, edit settings.json or hooks.json, run git commit --no-verify, force-push or rewrite history, choose a commit type prefix, a TaskUpdate gets blocked, or another session touched main today. Symptoms include "acceptance gate blocked me", "which commit type", "can I --no-verify this", "is it safe to force-push". Not for live symptom triage (mcs-debugging-playbook), "has this happened before" digs (mcs-failure-archaeology), or the config/flag catalog (mcs-config-and-flags).

0
installs
▌
Mcs Docs Of Record · dtsong bundle
Use when editing or auditing README.md, ARCHITECTURE.md, CONTRIBUTING.md, CHANGELOG.md, SECURITY.md, THIRD_PARTY_NOTICES.md, docs/, pipeline/specs/, or memory/HANDOVER-*.md in my-claude-setup, when two docs disagree on a number (agent/skill/command counts, token budgets, spec versions), when writing a handover or design doc, or when asked "which doc is right" or "is this stale". Not for skill-authoring mechanics (use mcs-claude-code-platform or the governance spec directly), release/novelty claims (use mcs-external-positioning), or live incident triage (use mcs-debugging-playbook).

0
installs
▌
Mcs Run And Operate · dtsong bundle
Use when running /council, /ship, /looper, or /handover day to day in this repo: choosing a council mode or --profile, resuming/listing/archiving a session, picking a Phase 5 execution path (team, ralf, launch, deep audit, issues export, Ship), reading or resuming .claude/ship-state.md or .claude/looper-state.md, writing a handover, or checking for an in-flight ship/council run before touching .claude/ state so you do not clobber it. Not for diagnosing why a hook or gate is silently failing (mcs-debugging-playbook) or for commit/PR/change-classification rules (mcs-change-control).

0
installs
▌
Mcs Analysis Toolkit · dtsong bundle
Use when you must prove a claim about this repo's token budgets, description trigger-reliability, hook-blocking behavior, multi-agent session cost, or a counter's trustworthiness before citing it in a review or merge decision, rather than eyeballing it or trusting a hook that merely looks wired. Covers hand-deriving token math, live-fire hook payloads, write-path-to-commit tracing, refute-first fix verification, each with a worked example. Not for routine tool invocation or exit-code reading (mcs-diagnostics-and-tooling), acceptance-evidence tiers (mcs-validation-and-qa), or the hunch-to-accepted-result idea lifecycle (mcs-research-methodology).

0
installs
▌
Mcs Config And Flags · dtsong bundle
Use when you need the current value, default, production/experimental/parked status, or enforcement guard for any Claude Code configuration axis in this repo, such as settings.json fields, env flags, permissions allow/deny lanes, hooks wiring, settings.local.json, council cost profiles, model-routing.json/yaml, budgets.json overrides, or security-suppressions.json, and when adding a brand-new configuration axis. Not for what a setting means at the Claude Code platform level (mcs-claude-code-platform) or for how a config change gets reviewed and merged (mcs-change-control).

0
installs
▌
Mcs Research Frontier · dtsong bundle
Use when scoping a genuinely open, publishable-flavor problem this repo could advance rather than a bug to fix or a feature to ship, e.g. "could this become a paper", "what's the interesting unsolved part here", "is anyone else doing this", or "what would make this evidence-worthy" for closed-loop skill evolution, heterogeneous multi-model council, contract-gated autonomous execution, config-as-production, or cross-session memory. Not for executing the OpenRouter/model-routing campaign itself (mcs-model-routing-campaign) or for how an idea graduates from hunch to accepted result (mcs-research-methodology).

0
installs
▌
Mcs Validation And QA · dtsong bundle
Use when deciding what counts as evidence in this repo, adding a pytest to mcp/openrouter, writing eval-cases/trigger-evals.json for a council department, flipping an acceptance-contract AC row to verified, running run-evals.sh or judge-skill-quality.sh, or someone claims a change "looks right" without a number or exit code. Covers hard vs warn pre-commit tiers, CI's actual (narrow) scope, and the acceptance-gate block mechanics. Not for running diagnostic tools themselves (mcs-diagnostics-and-tooling) or the history of why an enforcement gap exists (mcs-failure-archaeology).

0
installs
▌
Git Branches · dtsong
Use when listing local and remote branches or visualizing branch status and divergence.

0
installs
▌
Gh Tag · dtsong
Use when creating and pushing semantic version tags for a release cut.

0
installs
▌
Mcs Debugging Playbook · dtsong bundle
Use when a hook, gate, or check in this repo (my-claude-setup) seems armed but does nothing, or blocks when it shouldn't - a hook that should stop a tool call doesn't, TaskUpdate-to-completed is unexpectedly denied, /council's Workflow throws "requires args", /careful or /freeze does nothing, pre-commit fails on an untouched file, the openrouter MCP tool errors, or scripts/ recurses forever. Do NOT use for "has this been tried before" (mcs-failure-archaeology) or for measuring/profiling cost and reliability (mcs-diagnostics-and-tooling).

0
installs
▌
Gh Mine · dtsong
Use when listing GitHub issues and pull requests assigned to or mentioning the current user.

0
installs
▌
Mcs Failure Archaeology · dtsong bundle
Use when you need the history behind a file or decision before touching it, e.g. "has this been tried", "why was this deleted", "why is this branch stale", "is this issue real", or before reviving a branch, re-adding a deleted skill/hook/model-pin, or reopening an old issue. Covers the acceptance-gate saga, Fable-5 sweep, academy removal, OpenRouter Phase 1, branch graveyard, registry.json, privacy exposure. Not for live debugging (mcs-debugging-playbook) or why a design is load-bearing today (mcs-architecture-contract).

0
installs
▌
Soc Integration · dtsong
Use when planning SoC integration including bus fabric architecture, memory map allocation, IP qualification, interrupt routing, and design-for-test strategy. Covers AMBA/AXI protocols, register map design, DFT insertion, and production test planning. Do not use for RTL design flow (use chip-design-flow) or block-level verification (use verification-methodology).

0
installs
▌
Gh Issue · dtsong
Use when creating, linking, or managing GitHub issues with the repository's issue templates.

0
installs
▌
Mcs Claude Code Platform · dtsong bundle
Use when you need Claude Code platform mechanics as this repo actually wires them: writing or debugging a hook (stdin JSON payloads, which event plus exit code plus stream combination actually blocks), reading settings.json versus settings.local.json versus hooks.json, understanding why a skill or command loads twice, registering or calling an MCP server, or checking Workflow tool and agent-teams preflight. Not for this repo's commit rules and acceptance-gate incident history (mcs- change-control), the full config/flag value catalog (mcs-config-and-flags), or symptom-to-cause triage (mcs-debugging-playbook).

0
installs
▌
Mcs External Positioning · dtsong bundle
Use when deciding what this project (my-claude-setup) may claim publicly (README pitch, launch post, "why is this different" answers, OSS release announcements), when someone asks for a v1.0/launch readiness verdict against GitHub issue 3 (the v1.0 tracking issue), when evaluating third-party attribution or license compliance before a release, or when history/privacy exposure (real personal data reachable in pushed git refs) needs a decision framed for the owner. Not for fixing drifted docs (mcs-docs-of-record) or for open-research novelty claims (mcs-research-frontier).

0
installs
▌
Mcs Research Methodology · dtsong bundle
Use when turning a hunch into a shipped change here, deciding if a claim survives adversarial refutation before trusting it, writing a predicted number/exit-code/pass-rate before running an experiment or eval, tracing an idea through council deliberation, PRD non-goals, a numbered acceptance contract, gated /ship or /looper execution, to verified or retired, or picking settings.local.json as the experiment lane instead of settings.json. Not for measurement techniques (mcs-analysis-toolkit) or formal evidence tiers and AC mechanics (mcs-validation-and-qa).

0
installs
▌
Chip Design Flow · dtsong
Use when guiding RTL-to-GDSII chip design flow including RTL coding style, synthesis constraints, place-and-route strategy, timing closure, and tape-out checklist. Do not use for verification methodology (use verification-methodology) or SoC integration (use soc-integration).

0
installs
▌
Gh Health · dtsong
Use when producing a repository health dashboard covering CI, issues, and PR backlog status.

0
installs
▌
Gh Triage · dtsong
Use when batch labeling, prioritizing, and assigning GitHub issues during triage sessions.

0
installs
▌
Mcs Architecture Contract · dtsong bundle
Use when you need to know WHY this repo is built the way it is, not just what a file contains: shared engine plus themed layer, symlink deployment, backend degradation (workflow to teams to sequential), fail-soft contracts, progressive skill loading, session-state layering, and which invariants are enforced-by-hook versus prose-only. Also use to check a known-weak-point first: routing truth on three surfaces, unsynced session state, private-repo coupling. Do NOT use for step- by-step procedures (mcs-run-and-operate) or generic Claude Code platform mechanics (mcs-claude-code- platform).

0
installs
▌
Hw Security Signoff · dtsong
Use when a hardware design needs security sign-off before tape-out. Defines the builder-to-auditor handoff contract between Foundry (constructive design) and Forge (security review). Covers security review prerequisites, artifact checklist, sign-off criteria, and conditional approval workflow. Do not use for RTL security review itself (use rtl-security-review) or design flow guidance (use foundry/chip-design-flow).

0
installs
▌
Gh Release · dtsong
Use when creating a GitHub release with generated changelog notes and version tagging.

0
installs
▌
Mcs Model Routing Campaign · dtsong bundle
Use when consulting or extending the model-routing unification and OpenRouter multi-model council campaign in this repo (US-001..US-008, GitHub issues 59 to 66, council session claude-config-model-optimization-20260702-0003; track 1 completed 2026-07-06), checking phase state before touching .claude/ship-state.md or .claude/looper-state.md, mapping an issue to its acceptance criterion and test command, extending skills/council/model-routing.json, or judging whether OpenRouter Phase 2 lens-relay prerequisites (38-case harness, egress gates, fresh IDs, API key) are met. Not for generic ship/looper mechanics with no campaign context (mcs-run-and-operate), the full settings.json config-axis catalog (mcs-config-and-flags), or commit/PR review rules (mcs-change-control).

0
installs
▌
Gh Activity · dtsong
Use when summarizing recent repository activity across commits, pull requests, and issues.

0
installs
▌
Gh Pr Merge · dtsong
Use when merging a pull request with an explicit merge, squash, or rebase strategy.

0
installs
▌
Mcs Diagnostics And Tooling · dtsong bundle
Use when you need a hard number instead of an impression in my-claude-setup - skill/agent/command inventory counts, description-token cost, per-file or context-load token budgets, prose/checklist pattern scans, eval-tier runs, manual pre-commit validator exit codes, whether a hook actually blocks, or README-vs-reality drift. Covers pipeline/scripts/*, scripts/*, `python3 pipeline/hooks/check_*.py`, gh-based issue/PR/branch-protection queries, and this skill's own hook-contract-check.sh / doc-drift-check.sh. Not for deciding what counts as acceptance evidence (mcs-validation-and-qa) or for fixing what a tool finds (mcs-debugging-playbook).

0
installs
▌
Gh Changelog · dtsong
Use when generating a changelog from merged pull requests and commits since the last release.

0
installs
▌
Gh Pr Status · dtsong
Use when checking pull request status, CI results, review state, and merge readiness.

0
installs
▌
Gh Pr Update · dtsong
Use when updating a pull request branch with the latest changes from its base branch.

0
installs
▌
Verilator Simulation · dtsong
Use when planning or reviewing Verilator-based simulation workflows for SystemVerilog designs. Covers lint analysis, simulation setup, trace/waveform debugging, coverage-driven verification, and C++ co-simulation. Do not use for commercial EDA tools (use verification-methodology) or RTL design flow (use chip-design-flow).

0
installs
▌
Component Fix And Verify · dtsong bundle
Use when a diagnosed fix needs to be applied and verified against a Next.js component — "apply this fix," "fix and run tests," or "verify this change." Applies a single diagnosed fix with mandatory diff preview, then runs scoped and broad verification (tsc, lint, tests) with atomic safety and revert capability. Not for diagnosing bugs (use ui-bug-investigator or css-layout-debugger) or generating regression tests (use regression-test-generator).

0
installs
▌
Gh Pr Request · dtsong
Use when requesting reviewers on a pull request based on ownership and availability.

0
installs
▌
Gh Pr Respond · dtsong
Use when viewing and responding to pull request review comments thread by thread.

0
installs
▌
Regression Test Generator · dtsong bundle
Use when a verified fix needs a regression test — "write a test for this fix," "generate regression test," or "add test coverage for this bug." Auto-detects project test conventions, routes to Vitest+RTL or Playwright based on component type (sync vs async server), generates targeted tests with anti-brittleness constraints, and annotates coverage boundaries. Not for diagnosing bugs, applying fixes, or writing feature tests — use ui-bug-investigator, component-fix-and-verify, or manual test authoring respectively.

0
installs
▌
Verification Methodology · dtsong
Use when designing verification environments, planning coverage-driven closure, or architecting UVM testbenches. Covers constrained-random stimulus, functional coverage models, assertion-based verification, formal property checking, and coverage closure planning. Do not use for RTL design flow (use chip-design-flow) or SoC integration (use soc-integration).

0
installs
▌
Mcs Build And Env · dtsong bundle
Use when setting up my-claude-setup on a bare macOS machine, running or scripting install.sh (presets, flags, --uninstall, --dry-run, --conflict-policy), bootstrapping the mcp/openrouter venv, diagnosing "command not found", missing-symlink, or manifest errors during install, or verifying a fresh clone is healthy before first use. Not for day-to-day running of /council, /ship, or /looper (see mcs-run-and-operate) or for settings.json axis semantics and hook wiring (see mcs-config-and-flags).

0
installs
▌
Emerging Hw Security Skill · dtsong bundle
Use this skill when analyzing emerging hardware security paradigms — post-quantum cryptography hardware, chiplet/UCIe architectures, heterogeneous compute, or AI accelerator security. Triggers on "PQC hardware review", "UCIe security assessment", "NPU memory isolation", "chiplet trust boundary analysis". Covers migration risk from classical to post-quantum or monolithic to chiplet. Do NOT use for established microarchitectural attacks (use microarch-attack-skill) or kernel-level analysis (use kernel-security-skill).

1
install
▌
Python Data Engineering · dtsong bundle
Use this skill when writing Python code for data pipelines or transformations. Covers Polars, Pandas, PySpark DataFrames, dbt Python models, API extraction scripts, and data validation with Pydantic or Pandera. Common phrases: "Polars vs Pandas", "PySpark DataFrame", "validate this data", "Python extraction script". Do NOT use for SQL-based dbt models (use dbt-transforms) or integration architecture (use data-integration).

1
install
▌
Verification Scaffold Skill · dtsong bundle
Use this skill when generating verification artifacts from threat findings — SVA assertion templates, security review checklists, or tiered verification plans. Triggers on "generate assertions for these threats", "verification checklist", "SVA template", "map threats to verification". Expects upstream ThreatFinding input. Do NOT use for threat identification (use threat-model-skill) or compliance gap analysis (use compliance-pipeline-skill).

1
install
▌
Specialist Name · dtsong bundle
SPECIALIST_TRIGGER. Use when SPECIALIST_CONTEXT.

1
install
▌
Failure Mode Analysis · dtsong
Systematic failure scenario discovery and resilience mitigations

1
install
▌
Physical Design Security · dtsong
Use when reviewing physical implementation security for power domain coupling, timing-related leakage, clock domain crossing issues, and layout-level information exposure. Covers DPA/SPA resistance, EM emanation, fault injection countermeasures, and probing defenses. Do not use for RTL logic review (use rtl-security-review) or microarchitectural attack analysis (use microarch-analysis).

1
install
▌
Embedded Architecture · dtsong
Firmware design patterns, RTOS selection, memory and power management

1
install
▌
Physical Sca Skill · dtsong bundle
Use this skill when analyzing physical side-channel and fault injection attack surfaces — power analysis, electromagnetic emanation, voltage/clock/laser glitching, or combined attacks. Triggers on "DPA assessment", "fault injection resistance", "power side-channel review", "EM leakage analysis", "TVLA evaluation". Includes JIL scoring and ISO 17825 mapping. Do NOT use for microarchitectural side-channels (use microarch-attack-skill) or software-level isolation (use kernel-security-skill).

1
install
▌
Threat Model Skill · dtsong bundle
Use this skill when performing structured threat modeling for SoC hardware components — STRIDE analysis, attack tree construction, or standards-derived threat identification. Triggers on "threat model this block", "STRIDE analysis", "build an attack tree", "identify threats for". Covers Confidential AI, TDISP/CXL, Supply Chain, Secure Boot/DICE, and CHERI domains. Do NOT use for verification planning (use verification-scaffold-skill) or compliance tracking (use compliance-pipeline-skill).

1
install
▌
Intake Skill · dtsong bundle
Use this skill when scoping a new consulting engagement — "help me scope this project," "I need an engagement brief," or gathering client context through conversational clarification. Transforms natural-language descriptions into structured engagement briefs with targeted questions, sensitivity inference, and stakeholder mapping. Do NOT use for technology research (research-skill), risk assessment (assessment-skill), or client-facing deliverables (deliverable-skill).

1
install
▌
Research Skill · dtsong bundle
Use this skill when conducting structured technology research — "research these vendors," "do a landscape scan," "compare these technologies," or gathering evidence for consulting engagements. Performs source-orchestrated research with landscape scans, candidate profiling, evidence gathering, and comparative analysis producing findings for downstream assessment. Do NOT use for risk scoring (assessment-skill), engagement scoping (intake-skill), or client deliverables (deliverable-skill).

1
install
▌
Executive Brief Skill · dtsong bundle
Use this skill when translating technical security findings into executive communication — BLUF briefs, risk summary tables, or audience-adapted posture reports. Triggers on "executive summary of findings", "brief the CISO", "board-level security update", "summarize risks for leadership". Supports board, CISO, and program-level audiences. Do NOT use for technical analysis (use threat-model-skill or attack-domain specialists) or compliance tracking (use compliance-pipeline-skill).

1
install
▌
Kernel Security Skill · dtsong bundle
Use this skill when analyzing kernel security at the hardware/software interface — memory management, process isolation, privilege escalation paths, or IOMMU/SMMU configuration. Triggers on "kernel hardening review", "IOMMU bypass analysis", "privilege escalation audit", "container escape assessment", "KASLR/KPTI evaluation". Do NOT use for microarchitectural attacks (use microarch-attack-skill) or physical side-channels (use physical-sca-skill).

1
install
▌
Design System Architecture · dtsong
Token hierarchy, theming strategy, and cross-platform consistency

1
install
▌
Microarch Attack Skill · dtsong bundle
Use this skill when analyzing microarchitectural attack surfaces — transient execution, cache side-channels, branch predictor attacks, or shared-resource contention. Triggers on "Spectre analysis", "cache side-channel review", "check for Meltdown variants", "microarchitectural isolation audit". Covers CPU/GPU/accelerator components. Do NOT use for physical side-channels (use physical-sca-skill) or kernel-level privilege escalation (use kernel-security-skill).

1
install
▌
Tlaplus Security Skill · dtsong bundle
Use this skill when formalizing security properties into TLA+ specifications for model checking with TLC. Triggers on "formalize this security invariant", "TLA+ spec for this protocol", "model check this property", "write a TLA+ security spec". Translates threat findings and protocol behaviors into temporal logic. Do NOT use for threat identification (use threat-model-skill) or verification scaffolding without formal methods (use verification-scaffold-skill).

1
install
▌
AI Data Integration · dtsong bundle
Use this skill when connecting AI or LLMs to data platforms. Covers MCP servers for warehouses, natural-language-to-SQL, embeddings for data discovery, LLM-powered enrichment, and AI agent data access patterns. Common phrases: "text-to-SQL", "MCP server for Snowflake", "LLM data enrichment", "AI agent access". Do NOT use for general data integration (use data-integration) or dbt modeling (use dbt-transforms).

1
install
▌
Compliance Pipeline Skill · dtsong bundle
Use this skill when extracting requirements from security specifications, tracking compliance status, or producing gap analysis against hardware security standards. Triggers on "compliance check against DICE", "gap analysis", "extract requirements from spec", "FIPS compliance status", "ISO 21434 mapping". Covers DICE, TDISP, CXL, CHERI, SPDM, FIPS 140-3, and ISO 21434. Do NOT use for threat identification (use threat-model-skill) or executive communication (use executive-brief-skill).

1
install
▌
Github Issue · dtsong
Create, link, and manage GitHub issues with templates

1
install
▌
Journey Mapping · dtsong
Map complete user journeys with entry points, states, emotions, and decision points

1
install
▌
Protocol Analysis · dtsong
Use when analyzing cryptographic protocol security by modeling state machines, enumerating transitions, and identifying desynchronization, replay, downgrade, and session binding vulnerabilities. Covers protocol handshakes, session management, and negotiation integrity. Do not use for implementation-level crypto review (use crypto-review) or post-quantum assessment (use pqc-readiness).

1
install
▌
Microarch Analysis · dtsong
Use when analyzing microarchitectural attack surfaces by mapping shared hardware structures, identifying speculative execution vectors, quantifying speculative windows, and proposing countermeasures. Covers cache timing, transient execution, and contention channels. Do not use for RTL-level design review (use rtl-security-review) or physical implementation analysis (use physical-design-security).

1
install
▌
Deployment Plan · dtsong
Deployment strategy with rollback procedures, feature flags, and zero-downtime releases

1
install
▌
Library Evaluation · dtsong
Structured library scoring with popularity, maintenance health, bundle impact, and API quality

1
install
▌
Protocol Design · dtsong
Wireless protocol selection, stack design, and interoperability

1
install
▌
Github Health · dtsong
Repository health dashboard and status overview

1
install
▌
Github Triage · dtsong
Batch label and prioritize GitHub issues

1
install
▌
Pipeline Design · dtsong
Design data pipelines — ETL vs ELT, orchestration, batch vs streaming, idempotency, data quality, lineage

1
install
▌
Rtl Security Review · dtsong
Use when reviewing RTL designs for security vulnerabilities including access control gate bypasses, insecure FSM transitions, timing-dependent information leakage, and unintended data paths. Covers Verilog, SystemVerilog, and VHDL modules with security-critical functions. Do not use for physical implementation review (use physical-design-security) or microarchitectural attack analysis (use microarch-analysis).

1
install
▌
Growth Engineering · dtsong
Onboarding funnels, referral systems, and A/B test infrastructure

1
install
▌
Prompt Engineering · dtsong
System prompt design, chain-of-thought patterns, structured output, and prompt versioning

1
install
▌
Platform Audit · dtsong
Platform guideline compliance audit across iOS, Android, and web

1
install
▌
Invariant Analysis · dtsong
Use when enumerating security claims from a design, formalizing them as invariants, checking for hidden assumptions, and assessing verification feasibility. Covers safety invariants, temporal properties, and verification tool recommendations. Do not use for writing TLA+ specifications directly (use formal-spec) or implementation-level security review.

1
install
▌
Fleet Management · dtsong
Device provisioning, OTA update strategy, and fleet-scale monitoring

1
install
▌
Page Component Mapper · dtsong bundle
Use when investigating any frontend issue before diagnosis or debugging — maps a Next.js route to its full component tree. Resolves "what components render on this page," "show me the component tree for /dashboard," or "trace imports for this route." Produces a ComponentMap artifact with server/client boundaries, props, hooks, data fetching, and styling metadata consumed by all downstream QA skills. Not for diagnosing bugs, fixing code, or generating tests — those are handled by specialist skills after mapping is complete.

1
install
▌
Codebase Context · dtsong
Deep infrastructure analysis and context briefing for all council agents

1
install
▌
Pattern Analysis · dtsong
Audit codebase patterns and conventions, evaluate proposed changes for consistency

1
install
▌
Testing Strategy · dtsong
Design comprehensive test strategies with test pyramid coverage and quality gates

1
install
▌
Compliance Review · dtsong
GDPR/privacy compliance review for proposed features and data flows

1
install
▌
Monetization Design · dtsong
Pricing tiers, subscription architecture, and paywall strategy

1
install
▌
Competitive Analysis · dtsong
Feature comparison matrix across competing products and prior art

1
install
▌
Git Delete Branch · dtsong
Delete local and remote branches with safety checks

1
install

171 published skills · page 1 of 2