Grounded research. Traceability-first research workflow for evidence, reliability, product, policy, technical, sentiment, complaint, review, public-opinion, and source-backed questions. Use when the user asks for grounded research, rigorous research, exact…
asteasolutions/ai-toolkit
SkillsMP has collected 22 skills from asteasolutions/ai-toolkit. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 22
- GitHub stars
- 5
- GitHub forks
- 0
Skills in this repository
Showing 22 of 22 collected skills.
Evidence discipline for factual claims. Receipts before claims, no guessing, unknown is an allowed answer. Use as the baseline standard when citing sources, files, or command output, and when the user asks you to re-check an answer you already gave because…
use when the user wants a simple worded reply, or expresses that your speech is too complex, jargon-heavy, hard to understand etc. Or when they say "keep it simple"
Project an existing canonical .claude setup to GitHub Copilot, or fully AI-enable a repository for Claude Code and Copilot with shared instructions and the developer-led workflow. Re-runnable; converges the repo on the layout.
GitHub Copilot code review using thermo-nuclear correctness and code-quality rubrics. Use for pull request review, branch diffs, and review of added or modified code.
Sync issue-tracker tickets into docs/ markdown files. Use when the user wants to export or refresh project backlog docs from an issue tracker.
Answer questions about a project's context, issues, and domain by searching docs. Use when the user asks any question about project-level knowledge scoped to a named project folder under docs/.
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Comprehensive security and correctness audit of a branch's changes. Use for thermo nuclear, thermonuclear, or deep review requests, or branch/PR diff audits focused on bugs, breaking changes, security issues, devex regressions, and feature-gate leaks.
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module…
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, uses any 'grill' trigger phrases, or when another skill needs the grill.
Compact the current conversation into a handoff document for another agent to pick up.
Drive a development task — any size — through the developer-led loop (capture intent, plan, execute, reconcile), keeping the developer in control and oriented. Type `/helm <goal>` to start or resume.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Report the delta between a planned change and what was actually built — deviations, unplanned decisions, whether the result meets the intent, and any docs to update. Use to close out a task before calling it done, whenever a plan or spec was followed; helm's…
Install the /agentic-loop delegated build loop into this repo — orchestrator, implementer, and an independent reviewer that runs in its own context — fitted to the repo's existing layout.
Delegated build loop — approve a spec and its slices once, then implementation, verification, and independent review run without you. Type `/agentic-loop <goal>`.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Synthesize the settled conversation into a thin Plan on the work-tree leaf doc — no interview. Use when intent is pinned and you need a durable plan before building; helm's Plan phase reaches for this when the goal fits in one change.
Break a plan or conversation into tracer-bullet vertical slices as a work-tree map (_map.md + leaf docs). Local first; mirror to GitHub only when asked. Use when a goal is too big for one change; helm's Plan phase reaches for this on decomposition.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.