All authors
Claude Skills by tonone-ai
github.com/tonone-ai918 skills5 installs963 views
- Tune ReconAudit existing fine-tuning or prompt engineering work — find quality gaps and optimization opportunities.Votes: 0GitHub stars: 71
- Vect EmbedDesign an embedding pipeline — model selection, chunking, and indexing strategy.Votes: 0GitHub stars: 71
- Vect ReconAudit existing vector search or RAG implementation — find quality gaps and performance issues.Votes: 0GitHub stars: 71
- Vect SearchDesign a vector search or RAG system — retrieval strategy, reranking, and database selection.Votes: 0GitHub stars: 71
- Wire PrototypeDocument a prototype or user flow — screens, states, transitions, and annotations.Votes: 0GitHub stars: 71
- Wire ReconAudit existing design documentation — find gaps in specs, missing states, and handoff debt.Votes: 0GitHub stars: 71
- Wire SpecWrite a developer handoff spec for a component or feature — states, tokens, edge cases.Votes: 0GitHub stars: 71
- Zero AuditAudit an existing environment against zero trust principles — find implicit trust and over-privileged access.Votes: 0GitHub stars: 71
- Zero DesignDesign a zero trust architecture — phased roadmap, identity pillar, and network segmentation.Votes: 0GitHub stars: 71
- Zero ReconSurvey existing network and identity controls for zero trust readiness.Votes: 0GitHub stars: 71
- SKILL NAMESKILL_DESCRIPTIONVotes: 0GitHub stars: 71
- Apex ProfileScope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.Votes: 0GitHub stars: 71
- Apex ReconEngineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.Votes: 0GitHub stars: 71
- Apex StatsSpawn-count analytics for the tonone roster — which agents this project actually uses, from local session transcripts. Use when "which agents do we actually use", "show tonone stats", "prune the roster", or before running apex-profile.Votes: 0GitHub stars: 71
- Apex StatusCTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.Votes: 0GitHub stars: 71
- Apex TakeoverSystem takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".Votes: 0GitHub stars: 71
- ApexEngineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.Votes: 0GitHub stars: 71
- Atlas AdrWrite an Architecture Decision Record — document what was decided, why, what alternatives were considered, and what trade-offs were accepted. Use when asked to "write an ADR", "document this decision", or "why did we choose X".Votes: 0GitHub stars: 71
- Atlas ChangelogMaintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".Votes: 0GitHub stars: 71
- Atlas MapMap the system architecture — read the codebase, identify services and connections, output a C4-level architecture map as Mermaid diagrams with component descriptions. Use when asked to "map the architecture", "system diagram", "how does this work", or "architecture overview".Votes: 0GitHub stars: 71
- Atlas OnboardGenerate onboarding documentation — what this project does, how to set up locally, where things live, key decisions, how to deploy. Written for day-one engineers who know nothing. Use when asked for "onboarding docs", "new engineer guide", "how to get started", or "developer setup".Votes: 0GitHub stars: 71
- Atlas PresentGenerate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".Votes: 0GitHub stars: 71
- Atlas ReconDocumentation reconnaissance for takeover — find all docs, assess accuracy, freshness, coverage, and discoverability, and identify critical knowledge gaps. Use when asked "what docs exist", "documentation assessment", or "knowledge gaps".Votes: 0GitHub stars: 71
- Atlas ReportRender agent findings as a styled HTML report in the browser. Use when asked for "full report", "detailed report", "show in browser", or when CLI output exceeds the 40-line budget.Votes: 0GitHub stars: 71
- AtlasKnowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports. Use when asked to "write an ADR", "map the architecture", "document this decision", "onboarding docs", or "what changed".Votes: 0GitHub stars: 71
- Audit ControlsInternal legal controls review — approval workflows, contract lifecycle, access to sensitive docs. Use when asked to "audit our controls", "review approval workflows", or "who can access sensitive contracts".Votes: 0GitHub stars: 71
- Audit LegalFull legal compliance audit — contracts, policies, regulatory, IP, corporate hygiene. Use when asked to "run a legal audit", "are we legally compliant", or "full compliance review".Votes: 0GitHub stars: 71
- Audit ReconSurvey legal artifacts for audit readiness. Use when asked "are we audit ready", "what legal artifacts exist", or "survey our legal docs".Votes: 0GitHub stars: 71
- Axe AuditRun a WCAG accessibility audit against a component, page, or full product. Use when asked to "run an accessibility audit", "is this WCAG compliant", or "check a11y on this page".Votes: 0GitHub stars: 71
- Axe FixWrite accessibility fixes for specific WCAG failures — ARIA, focus management, keyboard patterns. Use when asked to "fix this accessibility issue", "add ARIA labels", or "make this keyboard navigable".Votes: 0GitHub stars: 71
- Axe ReconSurvey a codebase for accessibility debt — missing ARIA, broken keyboard patterns, and contrast issues. Use when asked "how accessible is our codebase", "find accessibility debt", or "where are our a11y gaps".Votes: 0GitHub stars: 71
- Bench CompareCompare API performance across versions — regression detection and root cause analysis. Use when asked "did performance regress", "compare API latency across versions", or "why is this slower".Votes: 0GitHub stars: 71
- Bench ProfileDesign a performance benchmark for an API — test scenarios, metrics, and tooling. Use when asked to "benchmark this API", "design a load test", or "measure throughput".Votes: 0GitHub stars: 71
- Bench ReconAudit existing performance testing — find missing benchmarks, stale baselines, and CI gaps. Use when asked "do we have benchmarks", "audit our performance testing", or "are our baselines stale".Votes: 0GitHub stars: 71
- Bind GapRun a compliance gap analysis against SOC2, GDPR, HIPAA, or ISO 27001. Use when asked "are we SOC2 ready", "run a GDPR gap analysis", or "what is missing for ISO 27001".Votes: 0GitHub stars: 71
- Bind PolicyDraft compliance policies required by a framework (access control, incident response, data retention). Use when asked to "write an access control policy", "draft our incident response policy", or "we need a data retention policy".Votes: 0GitHub stars: 71
- Bind ReconSurvey existing compliance artifacts — policies, audits, certifications. Use when asked "what compliance docs do we have", "survey our policies", or "inventory our compliance artifacts".Votes: 0GitHub stars: 71
- Blue DetectDesign detection rules for a threat — SIEM queries, alert logic, and MITRE ATT&CK mapping. Use when asked to "write a detection rule", "how do we detect this attack", or "build a SIEM query for this TTP".Votes: 0GitHub stars: 71
- Blue HardenWrite a hardening playbook for a system or service — CIS benchmark mapping and implementation steps. Use when asked to "harden this server", "apply the CIS benchmark", or "write a hardening playbook".Votes: 0GitHub stars: 71
- Blue ReconAudit existing security controls and detection coverage — find gaps against MITRE ATT&CK. Use when asked to "audit our detection coverage", "where are our security control gaps", or "check our MITRE coverage".Votes: 0GitHub stars: 71
- Brace EscalateDesign escalation path -- Tier 1 to Tier 2 to Engineering handoff, decision criteria, and communication templates. Use when asked to "design our escalation process", "when should support escalate to engineering", "build an escalation runbook", or "reduce escalation rate".Votes: 0GitHub stars: 71
- Brace KbBuild or audit knowledge base -- article structure, coverage gaps, deflection rate, and maintenance process. Use when asked to "build a knowledge base", "what docs are missing", "improve our self-serve rate", or "audit our help center".Votes: 0GitHub stars: 71
- Brace MetricsDesign support metrics dashboard -- CSAT, FRT, TTR, ticket deflection rate, volume trends, and agent efficiency. Use when asked to "what metrics should support track", "build our support dashboard", "measure support quality", or "audit our support performance".Votes: 0GitHub stars: 71
- Brace OnboardDesign customer support onboarding flow -- first-contact experience, proactive support touchpoints, and setup success checklist. Use when asked to "design our onboarding support", "how do we support new customers during onboarding", or "reduce early churn from setup failures".Votes: 0GitHub stars: 71
- Brace PlaybookWrite support playbook -- response templates, issue-type runbooks, tone guide, and common resolution paths. Use when asked to "write support templates", "build a support playbook", "train our support agents", or "standardize our support responses".Votes: 0GitHub stars: 71
- Brace ReconSupport operations reconnaissance -- audit current ticket volume, SLA compliance, knowledge base coverage, escalation paths, and CSAT to understand where support is the constraint. Use when asked to "audit our support", "why is our response time bad", "how healthy is our support operation", or "before designing a support system".Votes: 0GitHub stars: 71
- Brace SlaDesign SLA framework -- response time targets, resolution time targets, tier definitions, and breach escalation process. Use when asked to "define our SLAs", "what response times should we commit to", "build a support tier structure", or "set up SLA monitoring".Votes: 0GitHub stars: 71
- Brace TriageDesign ticket triage system -- routing rules, priority tags, queue structure, and first-response automation. Use when asked to "design our ticket routing", "how should we tag tickets", "set up our helpdesk", or "reduce time to first response".Votes: 0GitHub stars: 71
- Brief DraftDraft a contract or policy document from a description or template. Use when asked to "draft an NDA", "write an MSA", or "we need a vendor contract".Votes: 0GitHub stars: 71
- Brief ReconSurvey the project's existing contracts and policy docs. Use when asked "what contracts do we have", "survey our policy docs", or "inventory our agreements".Votes: 0GitHub stars: 71