Skill-uri pentru agenți pe care le poți verifica înainte să le instalezi
Skill-uri SKILL.md publice din depozite GitHub cu peste 50 de stele și de la producători, scanate și evaluate. Instalează oricare dintre ele cu o singură comandă în Claude Code, Cursor, Codex, GitHub Copilot sau Gemini CLI.
49.492 de skill-uri din 2.391 de depozite · actualizat acum 13 ore
48.451 de skill-uri
- minutes-debriefsilverstein/minutesPost-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.AlteleFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- receipts-auditmohitagw15856/pm-claude-skillsAudit any document against its own sources — every factual claim extracted and graded as evidenced, partially evidenced, unsupported, or contradicted, with the exact source line that supports or fails it. Use when asked to fact-check a document against its sources, check whether a report's claims are backed up, verify a deck against the data, or ask 'does this doc have receipts?'. Produces a claim ledger, unsupported claims ranked by load-bearingness, a fix-or-drop call per claim, and an honesty score with stated method.DocumenteFără avertismente★ 1,5 K↓ —
- incident-responserampstackco/claude-skillsManage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers when something is actively broken in production and the user is figuring out what to do.SecuritateFără avertismente★ 1 K↓ —
- code-review-assistantalibaba/skill-upTriggered when the user submits code or requests a code review. Automatically analyzes code quality, identifies potential bugs, security vulnerabilities, and performance issues, and provides improvement suggestions. Trigger phrases include "take a look at this code", "review this", "is there a problem with this function".InginerieFără avertismente★ 1,4 K↓ —
- cav-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a CAV (Computer Aided Verification) submission for portal readiness, covering the four submission categories (Regular / Short Tool / Short Application / Industrial Experience & Case Studies), the LNCS page limits, the per-category anonymization matrix, the artifact-intent declaration, and desk-reject triage before the AoE paper deadline.ȘtiințăFără avertismente★ 1,4 K↓ —
- eacl-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evidence for an EACL paper, covering tuned and LLM baselines, multilingual breadth matched to the claim, significance and variance floors, human-evaluation agreement, data-contamination controls, ablations, and error taxonomies, so that every stated result is measured rather than asserted.ȘtiințăFără avertismente★ 1,4 K↓ —
- dac-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or tightening the prose of an ACM/IEEE Design Automation Conference (DAC) Research Manuscript, covering the QoR-forward first-page arc, stating the design-automation contribution as a measured delta, fitting a complete argument into six double-column pages plus a references-only page, building column-width EDA figures, and third-person self-citation for double-blind review.RedactareFără avertismente★ 1,4 K↓ —
- minutes-debriefsilverstein/minutesPost-meeting debrief — analyzes what happened, compares outcomes to your prep intentions, tracks decision evolution. Use when the user says "debrief", "what just happened in that meeting", "what did we decide", "debrief that call", "post-meeting", "what changed", or right after stopping a recording.AlteleFără avertismente★ 1,6 K↓ —Apare și în 1 alt depozit
- cvpr-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental program of a CVPR paper, covering benchmark and baseline selection under matched-compute fairness, the ablation study reviewers treat as mandatory, qualitative and failure-case evidence, efficiency metrics tied to the Compute Reporting Form, and generalization tests beyond a single dataset.TestareFără avertismente★ 1,4 K↓ —
- imc-writing-stylebrycewang-stanford/Awesome-Journal-SkillsUse when drafting or revising the prose of an ACM IMC measurement paper, covering the first-page measurement finding, making vantage points and methodology auditable, longitudinal framing for a moving Internet, arguing limitations rather than reciting them, writing the Ethics section early, and acmart page-budget discipline.RedactareFără avertismente★ 1,4 K↓ —
- icdt-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ICDT (International Conference on Database Theory) regular-paper submission for Microsoft CMT readiness, covering the two-step abstract-then-paper deadline in the correct submission cycle, the lipics-v2021 15-page limit excluding references, the clearly-marked appendix read at the PC's discretion, anonymous submission since 2024, the complete-proofs / full-version expectation, and which submission problems are unfixable after the AoE cutoff.DateFără avertismente★ 1,4 K↓ —
- fse-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when deciding what belongs in an ESEC/FSE paper body versus its anonymized artifact and appendices, covering the ACM-template page budget, the rule that decision-critical evidence stays inside the reviewed pages, double-anonymous supplementary material, and how to split an empirical-SE paper between body and package.ȘtiințăFără avertismente★ 1,4 K↓ —
- icse-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the evaluation of an ICSE research-track paper, covering subject and benchmark selection, baseline fairness, statistical tests and effect sizes as SE reviewers expect them, qualitative-methods rigor, ablations for AI-based techniques, and threats-driven study design.TestareFără avertismente★ 1,4 K↓ —
- icdm-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the empirical evaluation for an ICDM (IEEE International Conference on Data Mining) paper - mining-task definition, strong and fairly-tuned baselines, ablations that isolate the named mechanism, scalability curves that test scale claims, and discovery-validity checks that separate real findings from evaluation artifacts.TestareFără avertismente★ 1,4 K↓ —
- icra-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing the experimental section of an ICRA paper — real-robot versus simulation-only evidence, trial counts and success-rate reporting, task distributions and resets, baseline fairness on shared hardware, sim-to-real transfer claims, failure-mode analysis, and the statistics robotics reviewers actually expect.ȘtiințăFără avertismente★ 1,4 K↓ —
- vis-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when designing or auditing IEEE VIS evaluations, covering how to match evidence to the contribution type (perceptual study, controlled user study, algorithm benchmark, design-study validation, qualitative work), controlled experiment design with power and effect sizes, CVD-safe and perceptually grounded encoding choices, task taxonomies, and provenance so a TVCG reviewer trusts the result.DesignFără avertismente★ 1,4 K↓ —
- cell-submissionbrycewang-stanford/Awesome-Journal-SkillsUse as the final preflight before submitting to Cell — a complete checklist across significance, narrative, Highlights/eTOC/Graphical Abstract, Summary, figures, STAR Methods, data, references, and required files. Bundles the checklist and cover-letter templates.ProductivitateFără avertismente★ 1,4 K↓ —
- hri-supplementarybrycewang-stanford/Awesome-Journal-SkillsUse when planning the supplementary materials for an ACM/IEEE HRI full paper — above all the video figure that shows the embodied interaction, plus study instruments, extended results, and appendices — deciding what a reviewer must see to judge the interaction versus what belongs outside the 8-page body, all anonymized for double-blind review.MediaFără avertismente★ 1,4 K↓ —
- hpca-experimentsbrycewang-stanford/Awesome-Journal-SkillsJournal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的 Claude Code/Codex 期刊技能包，从选题、识别策略到表格规范与审稿回复全流程，助你快速发论文。PlanificareFără avertismente★ 1,4 K↓ —
- focs-experimentsbrycewang-stanford/Awesome-Journal-SkillsUse when deciding whether and how computation appears in a FOCS (IEEE Symposium on Foundations of Computer Science) paper — a venue that accepts on theorems with no evaluation section expected — covering machine-verified case analyses, computer-discovered constructions, and honest illustrative plots.MediaFără avertismente★ 1,4 K↓ —
- experiment-designrampstackco/claude-skillsA discipline for designing experiments (A/B tests, multivariate, holdouts) so the results actually answer the question you asked. Hypothesis writing, sample size, duration, segment analysis, running discipline, matching a result to a pre-committed decision rule, and the common failure modes that produce confidently wrong shipping decisions. Use this skill whenever the user is planning a test that has not run yet: framing a hypothesis, sizing the sample, setting duration, choosing guardrails, or deciding whether something is worth testing at all. Triggers on design an experiment, experiment plan, A/B test, split test, multivariate test, holdout, experiment hypothesis, sample size, minimum detectable effect, MDE, test duration, guardrail metric, no peeking, pre-committed decision rule, is this worth testing. Use `experimentation-analytics` instead when the test has already run and the question is how to read the result panel.DesignFără avertismente★ 1 K↓ —
- ticket-authoringrampstackco/claude-skillsWrite complete, ready-to-pull work items for an issue tracker: bugs, tasks, stories, spikes, and epics, each with the fields, attachments, and done test its type requires. Use this skill whenever the user wants to write a ticket, create a Jira issue, Linear issue, or GitHub issue, file a bug report, write a user story or acceptance criteria, scope a spike, open an epic, or break work into tasks. Triggers on write a ticket, create an issue, file a bug, bug report, user story, spike, epic, task breakdown, turn this into tickets, break this down, acceptance criteria, definition of ready, ready for dev, backlog item, capitalization stage. Also triggers when the user pastes a PRD, a spec, or a bug description and asks what to do with it, even if they never say the word ticket.TestareFără avertismente★ 1 K↓ —
- planning-with-files-zhtOthmanAdi/planning-with-files用於多步驟 AI 代理工作的持久化檔案規劃。將 task_plan.md、findings.md 與 progress.md 保存在磁碟上，生命週期鉤子會注入選定的專案規劃內容。自動恢復只讀取專案規劃檔案；只有明確執行 session-catchup.py --metadata 才會檢查本機同一專案的代理工作階段中繼資料，--replay 則會輸出有界且以 nonce 框定的摘錄。選用的閘門模式只會在主機支援時要求繼續，而且絕不執行 Markdown 中宣告的命令。此技能沒有網路上傳路徑。適用於研究或需要超過 5 次工具呼叫的工作。觸發詞：任務規劃、專案計畫、制定計畫、分解任務、多步驟規劃、進度追蹤、檔案規劃、幫我規劃、拆解專案PlanificareFără avertismente★ 27,9 K↓ —
- brand-style-guiderampstackco/claude-skillsBuild or audit a comprehensive brand style guide that documents the full brand system including story, logo system, color, typography, imagery, voice, applications, and dos/don'ts. Use this skill whenever the user wants to create brand guidelines, document an existing brand, build a brand book, audit an existing style guide for completeness, or produce the artifact that other teams will reference for years. Triggers on style guide, brand guidelines, brand book, brand standards, brand manual, style sheet, brand documentation, brand reference. Also triggers when the brand identity is finished and needs to be documented for handoff to designers, developers, vendors, or future team members.DesignFără avertismente★ 1 K↓ —
secrets-vault-manager
alirezarezvani/claude-skills
DevOpsActualizat alaltăieri
De la autor
Use when setting up HashiCorp Vault, AWS Secrets Manager, Azure Key Vault or GCP Secret Manager, rotating secrets or auditing secret access. Generates config with vault_config_generator.py, plans rotation with rotation_planner.py and analyzes audit logs.
Instalare
npx skills add alirezarezvani/claude-skills --skill secrets-vault-manager -a claude-code
Se instalează în .claude/skills/secrets-vault-manager/ · Fiecare comandă descarcă skill-ul direct de pe GitHub cu utilitarul open source skills.
Descarcă .zip
Identic octet cu octet cu commit-ul scanat, cu licența depozitului și un fișier SOURCE.txt.
La ce are acces
Rulează scripturile incluseNu am văzut acces la rețeaLicență: MIT
Verificări de siguranță pe SKILL.md
- Include scripturi pe care nu le-am verificatScăzut
De ce 88
Securitate85
Proveniență94
Întreținere100
Licență100
Adopție69
Fișiere (7)
- SKILL.md
- references/cloud_secret_stores.md
- references/emergency_procedures.md
- references/vault_patterns.md
- scripts/audit_log_analyzer.py
- scripts/rotation_planner.py
- scripts/vault_config_generator.py