Agent skills you can check before you install
Public SKILL.md skills from GitHub repositories with 50+ stars and from the vendors themselves, scanned and scored. Install any of them with one command in Claude Code, Cursor, Codex, GitHub Copilot or Gemini CLI.
49,492 skills from 2,391 repositories · updated 6 hours ago
48,451 skills
- add-nativemicrosoft/power-platform-skillsPublic entry point for native device capabilities and native controls — camera, image picker, barcode/QR scanner, document picker, file picker, secure storage, file system, sharing, haptic feedback, PDF generation/viewing, pen/signature capture, background GPS/geolocation tracking, or supported local file workflows — in a Power Apps mobile app. Also owns routing to internal camera/PDF/pen/geolocation implementation helpers and the guidance boundary between native wrappers and Dataverse File/Image host controls.DocumentsNo warnings★ 1.1K↓ —
- saying-nomohitagw15856/pm-claude-skillsDecline a request, push back on scope, or protect priorities without burning the relationship. Use when asked how to say no, turn down a request, push back on your boss/stakeholder, decline extra work, or protect the roadmap from a pet feature. Produces a graceful, firm response — the no, the honest why, an alternative or trade-off, and the exact wording, tuned to who's asking.PlanningNo warnings★ 1.5K↓ —
- email-campaignmohitagw15856/pm-claude-skillsWrite and sequence multi-email nurture or launch campaigns. Use when asked for an email sequence, drip campaign, onboarding emails, product launch emails, or nurture flow. Produces subject lines, preview text, full email body, and send-timing recommendations for each email in the sequence.MarketingNo warnings★ 1.5K↓ —
- add-geolocationmicrosoft/power-platform-skillsInternal implementation skill invoked by /add-native for native background GPS tracking with durable storage and Dataverse sync using @microsoft/power-apps-native-bglocation.OtherNo warnings★ 1.1K↓ —
- org-chartmohitagw15856/pm-claude-skillsTurn a team or reporting structure into a clean org chart. Use when asked to draw an org chart, show reporting lines, visualize team structure, or map who reports to whom. Produces a ready-to-render Mermaid org chart (renders live, exportable as PNG/SVG) plus headcount notes and any structural observations.MediaNo warnings★ 1.5K↓ —
- osdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or managing a full OSDI cycle — the December title-registration and submission deadlines on HotCRP, the silent no-rebuttal review window, March notification, the May artifact deadline, June shepherded final papers, and the July conference — including rejection retargeting to SOSP or NSDI.ProductivityNo warnings★ 1.4K↓ —
- stoc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a STOC (ACM Symposium on Theory of Computing) project calendar — backward planning to the early-November deadline, the STOC/FOCS alternating two-deadline year that theory groups schedule around, full-version and camera-ready milestones, and the June TheoryFest endpoint.ProductivityNo warnings★ 1.4K↓ —
- nsdi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an NSDI campaign across the spring and fall deadlines — sequencing abstract and paper gates, notification waits, one-shot revision windows, artifact evaluation, and the May symposium — so a networked-systems project always knows which of the two yearly gates it is really building toward.ProductivityNo warnings★ 1.4K↓ —
- focs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning a FOCS (IEEE Symposium on Foundations of Computer Science) cycle end to end — working backward from the April 1 deadline, managing the live post-submission summer of the 2026 cycle, coordinating with the STOC beat, preparing the November conference, and scheduling a FOCS 2027 attempt.ProductivityNo warnings★ 1.4K↓ —
- podc-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM PODC campaign end to end — running the single annual cycle backward from the February deadline through abstract registration, lightweight double-blind review, the late-April notification, the May camera-ready, and the arXiv full version — and coordinating the regular-paper-vs-Brief-Announcement decision along the way.ProductivityNo warnings★ 1.4K↓ —
- icml-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning or sequencing an ICML manuscript workflow end to end - from topic selection and drafting through OpenReview submission, double-blind review, author response, camera-ready, PMLR publication, public original-submission release, and rerouting decisions. Use when you need the next ICML skill, the official page to reopen, or the blocking gap for the current stage.ProductivityNo warnings★ 1.4K↓ —
- itcs-workflowbrycewang-stanford/Awesome-Journal-SkillsUse to plan an ITCS campaign end to end on its single annual cycle — backward from the early-September deadline through the no-rebuttal review, the November notification, the LIPIcs camera-ready, and the January conference with its Graduating Bits session.ProductivityNo warnings★ 1.4K↓ —
- vis-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an IEEE VIS project timeline from area fit through the abstract and full-paper deadlines, the two-phase review, the conditional-accept second round, the IEEE TVCG camera-ready, the Graphics Replicability Stamp, and presentation, with backward-planning offsets for a visualization paper and honest handling of the annual cycle and the second-round revision window.ProductivityNo warnings★ 1.4K↓ —
- pnas-figuresbrycewang-stanford/Awesome-Journal-SkillsUse to finalize PNAS display items — column-width sizing (~9 / 11.4 / 18 cm), minimum font sizes, show-the-data with n and defined error bars, scale bars, colorblind-safe palettes, legend structure, image integrity, and color-mode notes. Enforces figure rigor before submission.MediaNo warnings★ 1.4K↓ —
- lancet-fitbrycewang-stanford/Awesome-Journal-SkillsUse when scoping a project and before any writing, to stress-test whether a study clears The Lancet's bar — clinically or public-health important, globally relevant, and likely to change practice or policy, often with an equity lens. Decides The Lancet vs a Lancet family title vs another general medical journal.TestingNo warnings★ 1.4K↓ —
- cell-rebuttalbrycewang-stanford/Awesome-Journal-SkillsUse after Cell reviews arrive to triage the decision, prioritize the (often substantial) new experiments by impact × feasibility, and draft a point-by-point response that is respectful, evidence-led, and closes the "completeness" gaps reviewers demand. Do not run before the experiments and revision are actually done.OtherNo warnings★ 1.4K↓ —
- review-fix-signoff-loopAgentWorkforce/relayUse when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents, typically Claude and Codex, both agree the work is comprehensively complete. Covers fresh-context iterations, repairable gates, dual reviewer verdict contracts, iteration-count reporting, PR signoff comments, and blocked-state handling.EngineeringNo warnings★ 1.1K↓ —
- choosing-swarm-patternsAgentWorkforce/relayUse when coordinating multiple AI agents with Agent Relay's workflow engine and need to pick the right orchestration pattern - covers the 10 core patterns (fan-out, pipeline, hub-spoke, consensus, mesh, handoff, cascade, dag, debate, hierarchical) plus 14 specialized ones, with decision framework and accurate SDK/YAML examples.PlanningNo warnings★ 1.1K↓ —
- cell-databrycewang-stanford/Awesome-Journal-SkillsUse to build Cell's data and code deposition plan and the Data and Code Availability statement that lives inside STAR Methods Resource Availability — approved repositories, accessions/DOIs at submission, and Cell's three-bullet availability format with Mendeley Data as Elsevier's default.PlanningNo warnings★ 1.4K↓ —
- chi-workflowbrycewang-stanford/Awesome-Journal-SkillsUse when planning an ACM CHI submission cycle end to end — the single September deadline, two-round review with a five-week revise-and-resubmit window, December decisions, the TAPS and publication-ready chain, and the May conference — with owners and risk buffers for each stage.ProductivityNo warnings★ 1.4K↓ —
- sci-databrycewang-stanford/Awesome-Journal-SkillsUse to build Science's data, code, and materials availability — mandatory deposition in approved repositories, accession numbers, a compliant data-availability statement, and materials/reagent sharing.ScienceNo warnings★ 1.4K↓ —
- review-fix-signoff-loopAgentWorkforce/relayUse when writing Agent Relay or Ricky workflows that must loop review, fix, and validation with fresh agent context until independent signoff agents, typically Claude and Codex, both agree the work is comprehensively complete. Covers fresh-context iterations, repairable gates, dual reviewer verdict contracts, iteration-count reporting, PR signoff comments, and blocked-state handling.EngineeringNo warnings★ 1.1K↓ —
- security-auditcloudflare/security-audit-skillSecurity guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.OfficialSecurityNo warnings★ 58.6K↓ —
- writing-guidelinesvercel-labs/agent-skillsReview docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".OfficialWritingNo warnings★ 33.5K↓ —
hf-cloud-sagemaker-iam-preflight
huggingface/skills
From the author
Ensure a usable SageMaker execution role exists before deploying or training. Use this skill whenever about to create a SageMaker endpoint, model, training job, or any resource that requires an execution role. Use it especially when the user has not provided a role ARN explicitly, when scripts are about to call `iam:CreateRole`, or when an AccessDenied error mentions an IAM action. Never blindly call `iam:CreateRole` — always check for existing roles first. This skill prevents the most common SageMaker deployment failure: trying to create IAM resources from an SSO principal that has no IAM write permissions.
Install
npx skills add huggingface/skills --skill hf-cloud-sagemaker-iam-preflight -a claude-code
Installs to .claude/skills/hf-cloud-sagemaker-iam-preflight/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
What it can touch
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 88
Files (5)
- SKILL.md
- references/minimum-permissions.json
- references/trust-policy.json
- scripts/check_role.py
- scripts/create_role.py