ai-explore
De la autor
Answers questions about this repository by reading it, anchored to file:line, and tours an unfamiliar area for somebody who has just arrived. Trigger for "where does X live", "how does this work", "why does it do that", "what depends on Y", "walk me through", "map this module", "trace this import chain", "onboard me". Not for evidence from outside this repository — use /ai-research. Not for diagnosing a failure — use /ai-debug. Not for judging a diff — use /ai-verify.
Instalare
npx skills add arcasilesgroup/ai-engineering --skill ai-explore -a claude-code
Se instalează în .claude/skills/ai-explore/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
Vrei ca agentul să-ți propună skill-uri în timp ce scrii? Vezi cum folosești skill-urile din IDE.
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 82
aiqbench calculează scorul de încredere din semnale publice. Nu este un audit de securitate, așa că citește un skill înainte să-l instalezi.
Skill-uri similare
Cele mai apropiate de acesta prin ce fac și când sunt folosite.
- ai-researcharcasilesgroup/ai-engineeringFinds evidence from outside this repository and reports it with numbered citations, or marks a claim [unsourced] and leaves it marked. Uses only the tools the client actually has: the local floor is always on, web search / Tavily / Exa run only when the client configured them, and NotebookLM deep research runs only when `notebooklm doctor` passes — an absent tool degrades and is named, never an error. Ends with three cited directions worth taking. Trigger for "what does the state of the art say", "compare the options for", "find sources on", "is this still true", "what do the docs say about". Not for questions whose answer is in this repository — use /ai-explore. Not for diagnosing a failure — use /ai-debug. Not for deciding what to build — use /ai-orchestrator.Știință★ 62
- ai-debugarcasilesgroup/ai-engineeringFinds the root cause of broken behaviour and names it at file:line, then writes the check that fails for that reason before changing anything. Also resolves merge and rebase conflicts by intent rather than by taking a side. Trigger for "it's not working", "this used to work", "I'm getting an error", "CI is failing", "why is X happening", "I have conflicts", "the rebase failed". Not for adding test coverage to working code — use /ai-verify. Not for exploring an unfamiliar area — use /ai-explore. Not for designing the fix — once the cause is named, use /ai-orchestrator. Not for reporting the fault to outsiders — use /ai-issue-report.Inginerie★ 62
- onboardOutlineDriven/outline-driven-developmentUse when the user asks for onboarding, orientation, a repository tour, or where to start. Produces an evidence-backed seven-section map, deep-reads real files, and asks for the next move.Altele★ 55
- ai-read-docsarcasilesgroup/ai-engineeringUse when the work depends on versioned or external behaviour — adding a package, writing setup or config, integrating an SDK or a paid API, debugging a framework change — or on anything involving third-party APIs, libraries, frameworks, CLIs, cloud services, model/provider SDKs, fast-moving product behavior, user requests for latest/current/official behavior, unfamiliar repo docs/specs, errors that may indicate API drift, or high-stakes auth, security, billing, data, migration, deployment, compliance, or privacy behavior. Forces a docs pass (web-search of official sources) and reading primary docs before assuming from memory. Not for evidence from outside this repository generally — use /ai-research; not for questions the repository answers — use /ai-explore.Securitate★ 62
- literature-researchfcakyon/phd-skillsUse when the user wants to find related work, survey a research area, identify literature gaps, or discover open-source implementations. Triggers on phrases like "find papers on", "related work", "literature review", "what papers exist", "open source implementation", or "papers with code".Știință★ 436
- researchOyadotAI/oya-browserThis skill should be used when researching a technical question, checking current API facts, comparing documented capabilities, or gathering primary-source evidence for a decision.Știință★ 348
Note și recenzii
—
nicio recenzie
Ai încercat acest skill? Notează-l ca să-i ajuți pe alții. Autentifică-te
Discuție
Intră în discuție. Autentifică-te