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 2 ore
49.492 de skill-uri
- soda-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a SODA (ACM-SIAM Symposium on Discrete Algorithms) campaign end to end — backward-planning to the July AoE deadline, SODA's seat in the theory calendar between STOC and FOCS deadlines, the September rebuttal and October decision, satellite deadlines (ALENEX, SOSA), and the January conference.ProductivitateFără avertismente★ 1,4 K↓ —
- pmla-workflowbrycewang-stanford/Awesome-Journal-SkillsUse as the entry point for any PMLA (Publications of the Modern Language Association) manuscript. Routes to the right PMLA sub-skill based on where you are in the lifecycle and which venue fits — a regular blind-reviewed article or a special feature (Theories and Methodologies, The Changing Profession, Criticism in Translation, Little-known Documents). It dispatches; it does not draft content.ProductivitateFără avertismente★ 1,4 K↓ —
- pnas-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to PNAS's numbered citation style — cited in order of appearance, a numbered reference list, full author lists, abbreviated journal titles. Provides formats for article/book/chapter/dataset/preprint and an author-date → PNAS conversion table. Late-stage style pass.MarketingFără avertismente★ 1,4 K↓ —
- pldi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a PLDI campaign across its annual clock — backward-planning from the November deadline through winter reviewing, the February response window, March notification, post-acceptance artifact evaluation, PACMPL production, and the June conference, with owners for each deliverable.ProductivitateFără avertismente★ 1,4 K↓ —
- pnas-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the PNAS abstract — a single self-contained paragraph of ~250 words, quantified and accessible to a broad scientific audience. Distinguishes the abstract (what/how/found, for scientists) from the Significance Statement (why-it-matters, for everyone). Late-stage polish.ȘtiințăFără avertismente★ 1,4 K↓ —
- pnas-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after PNAS reviews arrive to triage the decision, prioritize experiments, and draft a point-by-point response that is respectful, evidence-led, and honest about limits. Do not run before the main text is actually revised.AlteleFără avertismente★ 1,4 K↓ —
- pnas-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which pnas-* sub-skill to invoke next, or when sequencing a manuscript from significance test through reviewer rebuttal for PNAS (Proceedings of the National Academy of Sciences). Routes — it does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- documenthashgraph-online/awesome-codex-pluginsRecord a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.ȘtiințăFără avertismente★ 1,5 K↓ —
- nejm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which nejm-* sub-skill to invoke next, or when sequencing a clinical manuscript from significance test through response to reviewers for The New England Journal of Medicine. Routes — it does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- ndss-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NDSS submission calendar — choosing between the summer and fall cycles, backward-planning from the AoE deadline through early-reject, rebuttal, notification, camera-ready, and the Seoul symposium, and placing NDSS honestly inside the security big-four retargeting year.ProductivitateFără avertismente★ 1,4 K↓ —
- nejm-citationbrycewang-stanford/Awesome-Journal-SkillsUse to convert references to NEJM's Vancouver / ICMJE numbered style — numbered in order of appearance, limited author lists then et al., NLM journal abbreviations, and a capped reference count. Late-stage style pass.AlteleFără avertismente★ 1,4 K↓ —
- kdd-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing a KDD submission for readiness in either cycle, covering Research vs ADS track declaration, OpenReview profile completeness for all authors, the ACM sigconf 8-content-page budget, double-blind checks, in-paper artifact references, resubmission declarations, and desk-reject triggers specific to ACM SIGKDD.ȘtiințăFără avertismente★ 1,4 K↓ —
- nejm-abstractbrycewang-stanford/Awesome-Journal-SkillsUse to write the NEJM structured abstract — four headed sections (Background, Methods, Results, Conclusions), ≤250 words, with the trial registration number and funding source, leading the Results with the primary outcome reported as an effect size with a 95% CI. Late-stage polish skill.RedactareFără avertismente★ 1,4 K↓ —
- icse-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICSE research-track campaign end to end, covering the single-cycle calendar from the June abstract deadline through September response, October decisions, the November revision sprint, artifact evaluation, camera-ready, and the April conference, plus rerouting timelines after rejection.ProductivitateFără avertismente★ 1,4 K↓ —
- product-discoveryalirezarezvani/claude-skillsValidate product ideas: map assumptions, plan discovery sprints, test problem-solution fit. Use whenever the user asks if an idea is worth building.TestareFără avertismente★ 29,3 K↓ —
- jama-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when deciding which jama-* sub-skill to invoke next, or when sequencing a clinical manuscript from scope check through revision for JAMA (Journal of the American Medical Association). Routes — does not replace — the specialized skills.ProductivitateFără avertismente★ 1,4 K↓ —
- isca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a full ISCA campaign on a calendar — working back from the expected mid-November abstract and paper deadlines to freeze simulation evidence in time, staffing the winter two-round review wait, preparing for the February-March rebuttal and revision window, and branching to camera-ready, artifacts, and the June conference.ProductivitateFără avertismente★ 1,4 K↓ —
- icra-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICRA submission calendar end to end — the September paper deadline, the two video-attachment windows, winter review silence, late-January notification, March camera-ready, and the May/June conference — or when interleaving a fallback RA-L or IROS plan around the single annual ICRA shot.ProductivitateFără avertismente★ 1,4 K↓ —
- imc-submissionbrycewang-stanford/Awesome-Journal-SkillsUse when auditing an ACM IMC submission for HotCRP readiness, covering the paper-registration step, the acmart template with BBL upload, the full/short page limits, double-blind anonymity including vantage-point details, the mandatory Ethics section, the artifact-availability declaration, cycle choice, and desk-reject triage before the AoE cutoff.ȘtiințăFără avertismente★ 1,4 K↓ —
- ipsn-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IPSN-lineage project timeline from track/venue selection through the CPS-IoT Week deadline, double-blind submission, deployment and hardware logistics, rebuttal, the Best Research Artifact Award, and the dual ACM/IEEE camera-ready — with honest handling of the fact that IPSN merged into SenSys.ProductivitateFără avertismente★ 1,4 K↓ —
- icdt-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDT (International Conference on Database Theory) campaign end to end, running the two-submission-cycle calendar backward from a chosen cycle deadline through abstract registration, the first-cycle revision round, LIPIcs camera-ready, and presentation at the co-located EDBT/ICDT event.ProductivitateFără avertismente★ 1,4 K↓ —
- iccv-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when project-managing an ICCV campaign across the odd-year cycle, covering the autumn fork between CVPR and ICCV, the early-March registration and single submission deadline, May rebuttal week, late-June decisions, the October conference with international travel and visa lead times, and the ECCV/CVPR fallback ladder if the paper misses.ProductivitateFără avertismente★ 1,4 K↓ —
- icdm-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ICDM (IEEE International Conference on Data Mining) project timeline from venue fit through the abstract and full-paper deadlines, the long summer wait to the August notification, the no-rebuttal review, the possible short-paper acceptance branch, IEEE camera-ready, and in-person presentation on a single annual deadline.ProductivitateFără avertismente★ 1,4 K↓ —
- hpca-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an HPCA project timeline from venue fit through the two-step July registration and paper gate, the autumn review wait, the single rebuttal/revision window, notification, IEEE camera-ready, artifact evaluation, and the February/March talk, with backward-planning offsets for a hardware-evaluated paper.ProductivitateFără avertismente★ 1,4 K↓ —
endpoint-probe
hoangsonww/Claude-Code-Agent-Monitor
DateActualizat acum 17 ore
De la autor
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
Instalare
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill endpoint-probe -a claude-code
Se instalează în .claude/skills/endpoint-probe/ · 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
Doar instrucțiuniNu am văzut acces la rețeaLicență: MIT
Verificări de siguranță pe SKILL.md
Niciun avertisment.
De ce 88
Securitate100
Proveniență77
Întreținere100
Licență100
Adopție49
Fișiere (2)
- SKILL.md
- agents/openai.yaml