1,061 Open Skills

Free to get · One-click to use

✅ AI semantic search & keyword search
✅ Discussions & community interaction
✅ Version updates & multi-metric ranking
✅ Open SKILL.md standard

Import Skills

Composite Most Downloads Most Likes Most Comments Newest
westonwrz westonwrz
from GitHub Testing & Security
  • 📁 agents/
  • 📁 references/
  • 📄 SKILL.md
claims token security

authentik

Design, secure, and operate authentik-based OIDC integrations for production systems. Use for application/provider setup, scopes and claims mapping, redirect URI policy, token/session lifetime decisions, signing key management, and incident-ready operations. --- # Authentik ## Workflow 1. Confirm identity architecture, trust boundaries, and app risk profile. 2. Model tenants, applications, and OAuth2/OIDC providers. 3. Configure redirect URI policy and client type correctly. 4. Define scopes, claims/property mappings, and subject strategy. 5. Set token/session lifetimes aligned with threat model. 6. Validate metadata, login/logout flows, and key rotation behavior. 7. Operationalize monitoring, audit logs, and recovery runbooks. ## Preflight (Ask / Check First) - Authentik version and deployment mode. - Public vs confidential client usage. - Required claims and group/role mapping expectations. - Session and token lifetime requirements. - TLS, reverse-proxy, and domain model. ## Provider and Application Modeling - Create one provider per application trust boundary. - Choose `client_type` correctly (`public` vs `confidential`). - Keep redirect URI matching strict unless a strong regex case exists. - Separate human login apps from machine-to-machine access paths. - Keep issuer mode explicit per provider where needed. ## Scopes, Claims, and Subject Design - Minimize default scopes; add optional scopes intentionally. - Use property mappings to control claim release. - Preview claims per user before production enablement. - Prefer stable subject strategy for downstream account linking. - Avoid overloading ID tokens with unnecessary claims. ## Token and Session Security - Keep access token validity short. - Scope refresh token lifetime to business need. - Require strong signing key hygiene and rotation procedures. - Validate logout/end-session endpoints for all relying parties. - Protect client secrets in secret stores, never in repo config. ## Integration Guardrails - Vali

⬇0 ❤2 20小时前·上传 Detail →

Skill File Structure Sample (Reference)

skill-sample/
├─ SKILL.md              ⭐ Required: skill entry doc (purpose / usage / examples / deps)
├─ manifest.sample.json  ⭐ Recommended: machine-readable metadata (index / validation / autofill)
├─ LICENSE.sample        ⭐ Recommended: license & scope (open source / restriction / commercial)
├─ scripts/
│  └─ example-run.py     ✅ Runnable example script for quick verification
├─ assets/
│  ├─ example-formatting-guide.md  🧩 Output conventions: layout / structure / style
│  └─ example-template.tex         🧩 Templates: quickly generate standardized output
└─ references/           🧩 Knowledge base: methods / guides / best practices
   ├─ example-ref-structure.md     🧩 Structure reference
   ├─ example-ref-analysis.md      🧩 Analysis reference
   └─ example-ref-visuals.md       🧩 Visual reference

More Agent Skills specs Anthropic docs: https://agentskills.io/home

SKILL.md Requirements

├─ ⭐ Required: YAML Frontmatter (must be at top)
│  ├─ ⭐ name                 : unique skill name, follow naming convention
│  └─ ⭐ description          : include trigger keywords for matching
│
├─ ✅ Optional: Frontmatter extension fields
│  ├─ ✅ license              : license identifier
│  ├─ ✅ compatibility        : runtime constraints when needed
│  ├─ ✅ metadata             : key-value fields (author/version/source_url...)
│  └─ 🧩 allowed-tools        : tool whitelist (experimental)
│
└─ ✅ Recommended: Markdown body (progressive disclosure)
   ├─ ✅ Overview / Purpose
   ├─ ✅ When to use
   ├─ ✅ Step-by-step
   ├─ ✅ Inputs / Outputs
   ├─ ✅ Examples
   ├─ 🧩 Files & References
   ├─ 🧩 Edge cases
   ├─ 🧩 Troubleshooting
   └─ 🧩 Safety notes

Why SkillWink?

Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.

We provide AI semantic + keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.

AI Semantic Search Keyword Search Version Updates Multi-Metric Ranking Open Standard Discussion

Quick Start:

Import/download skills (.zip/.skill), then place locally:

~/.claude/skills/ (Claude Code)

~/.codex/skills/ (Codex CLI)

One SKILL.md can be reused across tools.

FAQ

Everything you need to know: what skills are, how they work, how to find/import them, and how to contribute.

1. What are Agent Skills?

A skill is a reusable capability package, usually including SKILL.md (purpose/IO/how-to) and optional scripts/templates/examples.

Think of it as a plugin playbook + resource bundle for AI assistants/toolchains.

2. How do Skills work?

Skills use progressive disclosure: load brief metadata first, load full docs only when needed, then execute by guidance.

This keeps agents lightweight while preserving enough context for complex tasks.

3. How can I quickly find the right skill?

Use these three together:

  • Semantic search: describe your goal in natural language.
  • Multi-filtering: category/tag/author/language/license.
  • Sort by downloads/likes/comments/updated to find higher-quality skills.

4. Which import methods are supported?

  • Upload archive: .zip / .skill (recommended)
  • Upload skills folder
  • Import from GitHub repository

Note: file size for all methods should be within 10MB.

5. How to use in Claude / Codex?

Typical paths (may vary by local setup):

  • Claude Code：~/.claude/skills/
  • Codex CLI：~/.codex/skills/

One SKILL.md can usually be reused across tools.

6. Can one skill be shared across tools?

Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.

Example: retrieval + writing + automation scripts as one workflow.

7. Are these skills safe to use?

Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.

8. Why does it not work after import?

Most common reasons:

  • Wrong folder path or nested one level too deep
  • Invalid/incomplete SKILL.md fields or format
  • Dependencies missing (Python/Node/CLI)
  • Tool has not reloaded skills yet

9. Does SkillWink include duplicates/low-quality skills?

We try to avoid that. Use ranking + comments to surface better skills:

  • Duplicate skills: compare differences (speed/stability/focus)
  • Low quality skills: regularly cleaned up