Find the best CLAUDE.md, AGENTS.md and Claude skills

AnthropicSkill

analyzing-financial-statements

anthropics/claude-cookbooks/skills/custom_skills/analyzing-financial-statements/SKILL.md

This skill calculates key financial ratios and metrics from financial statement data for investment analysis

AnthropicSkill

applying-brand-guidelines

anthropics/claude-cookbooks/skills/custom_skills/applying-brand-guidelines/SKILL.md

This skill applies consistent corporate branding and styling to all generated documents including colors, fonts, layouts, and messaging

AnthropicSkill

creating-financial-models

anthropics/claude-cookbooks/skills/custom_skills/creating-financial-models/SKILL.md

This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions

JetBrainsAGENTS.md

kotlin

JetBrains/kotlin/AGENTS.md

CRITICAL: guidelines.md MUST be followed at all times.

No other project uses it yet

JetBrainsAGENTS.md

kotlin / analysis

JetBrains/kotlin/analysis/AGENTS.md

A library for analyzing Kotlin code at the semantic level, providing structured access to symbols, types, and semantic relationships. Entry point: Use analyze() to start an analysis session. See Analysis…

No other project uses it yet

JetBrainsCLAUDE.md

kotlin

JetBrains/kotlin/CLAUDE.md

CRITICAL: @./.ai/guidelines.md guidelines MUST be followed at all times. Local Preferences: @./.claude/local.md When asked to update memory, you must update ./.claude/CLAUDE.md if it is not specified that another file should…

No other project uses it yet

JetBrainsSkill

analysis-api-create-cherry-pick-issue

JetBrains/kotlin/.claude/skills/analysis-api-create-cherry-pick-issue/SKILL.md

Create a KTIJ cherry-pick tracking issue for a KT fix that needs to be cherry-picked to an IntelliJ branch. Use when cherry-picking Analysis API fixes.

No other project uses it yet

JetBrainsSkill

analysis-api-mark-internal-apis

JetBrains/kotlin/.claude/skills/analysis-api-mark-internal-apis/SKILL.md

Drive the per-module internal-API codebase test, then refine the suggested annotations down to `internal` (or up to `@KaImplementationDetail`) based on actual external usage

JetBrainsSkill

build-bump-gradle-version

JetBrains/kotlin/.claude/skills/build-bump-gradle-version/SKILL.md

Bumps the Gradle wrapper/distribution version that BUILDS the Kotlin project itself — the version behind `./gradlew`, defined by `gradle/wrapper/gradle-wrapper.properties`. Covers the wrapper regeneration and the version-specific fallout that follows it: removed/deprecated Gradle DSL, dependency-verification metadata, the Gradle Module Metadata fixtures, and the KGP functional tests. This is DISTINCT from the two sibling skills — it is NOT `build-tools-bump-gradle-api` (which bumps GRADLE_COMMON_COMPILE_API_VERSION, the API that plugins compile against) and NOT `build-tools-bump-gradle-in-tests` (which extends the KGP integration-test version matrix). Manual invocation only: a full run downloads a distribution, rewrites `gradle/verification-metadata.xml`, and drives `publish`, `testClasses` and `functionalTest` — hours of wall clock and a heavily mutated checkout — so it starts only when the user explicitly asks for `/build-bump-gradle-version`.

JetBrainsSkill

build-tools-add-test-federation-annotations-to-integration-tests

JetBrains/kotlin/.claude/skills/build-tools-add-test-federation-annotations-to-integration-tests/SKILL.md

Annotate test classes in `kotlin-gradle-plugin-integration-tests` with Test Federation annotations (`@MustRunOnChangesInXYZ` / `@MustRunAlways`). Use this whenever the user asks to annotate, review, or fix Test Federation annotations on an integration test class, or to assess a test class for cross-domain dependencies under Test Federation (KT-87614).

JetBrainsSkill

build-tools-bump-gradle-api

JetBrains/kotlin/.claude/skills/build-tools-bump-gradle-api/SKILL.md

Bumps the Gradle API version that Kotlin Gradle plugins are compiled against in the Kotlin compiler repository. Use this skill whenever the user asks to upgrade, bump, or update the Gradle compile API version, Gradle plugin API version, or GRADLE_COMMON_COMPILE_API_VERSION. Also use it when the user says something like "update KGP to compile against Gradle X.Y.Z" or "bump Gradle API to X.Y" or "we need to support Gradle X.Y in the plugin".

JetBrainsSkill

build-tools-bump-gradle-in-tests

JetBrains/kotlin/.claude/skills/build-tools-bump-gradle-in-tests/SKILL.md

Bump the maximum supported Gradle version in the `kotlin-gradle-plugin-integration-tests` project. Use this whenever the user asks to bump Gradle in integration tests, add a new Gradle X.Y.Z to the test matrix, update `MAX_SUPPORTED` Gradle, "run tests against the new Gradle release", or anything else that sounds like extending the integration test matrix to a newer Gradle. The procedure spans four touch points across three files that must stay in lock-step (`TestVersions.kt`, `build.gradle.kts`, `GradleCompatibilityIT.kt`); reach for this skill even when the user mentions only one of those files, because editing by hand routinely desyncs them.

JetBrainsSkill

minimize-repro-for-diagnostic-test

JetBrains/kotlin/.claude/skills/minimize-repro-for-diagnostic-test/SKILL.md

Makes a minimal reproduction of a Frontend-related bug as a diagnostic test

JetBrainsAGENTS.md

kotlin / compiler

JetBrains/kotlin/compiler/AGENTS.md

Consider reading fir-basics.md. FIR processes code through sequential phases (see FirResolvePhase.kt). Key invariant: In phase B following phase A, all FIR elements visible in B are resolved to phase A.

No other project uses it yet

AppleSkill

container

apple/container/skills/container/SKILL.md

Use when running, building, or managing Linux containers on macOS, or when a task involves Docker, docker compose, Lima, Colima, or Podman commands on a Mac, Dockerfiles, OCI images, image registries, or setting up a Linux development environment on Apple silicon.

AstralAGENTS.md

ruff

astral-sh/ruff/AGENTS.md

This repository contains both Ruff (a Python linter and formatter) and ty (a Python type checker). The crates follow a naming convention: ruff_* for Ruff-specific code and ty_* for ty-specific code. ty reuses several Ruff crates, including the Python parser (ruff_python_parser) and AST definitions (ruff_python_ast). Before starting work on an issue and again before opening a pull request, follow the guidance on avoiding duplicate work. If an open pull request already addresses the issue, do not submit a competing one…

No other project uses it yet

AstralSkill

adding-ty-diagnostics

astral-sh/ruff/.agents/skills/adding-ty-diagnostics/SKILL.md

Use when a user says "add a ty rule", "add a ty diagnostic", "write this new ty diagnostic", "change a ty error message", "review ty diagnostics", or asks to add, update, or review ty checks, diagnostic messages, subdiagnostics, or concise output behavior.

AstralSkill

minimizing-ty-ecosystem-changes

astral-sh/ruff/.agents/skills/minimizing-ty-ecosystem-changes/SKILL.md

Use when a user says "minimize this ty ecosystem change", "reproduce this ecosystem result", "investigate a primer difference", "investigate a mypy_primer difference", "investigate a mypy-primer difference", or asks to reproduce, investigate, or minimize behavior changes in ty ecosystem/primer/mypy_primer/mypy-primer projects.

AstralSkill

review-ty-changes

astral-sh/ruff/.agents/skills/review-ty-changes/SKILL.md

Review ty changes in astral-sh/ruff, including pull requests and local changes just written by a user or an agent. Use when asked to review, re-review, audit, or inspect ty changes for correctness, regressions, architecture, maintainability, test coverage, unnecessary complexity, or meaningful style and consistency issues.

AstralSkill

summarise-ecosystem-results

astral-sh/ruff/.agents/skills/summarise-ecosystem-results/SKILL.md

Use when a user says "summarise ecosystem results", "summarize this ty ecosystem report", "what changed in this ecosystem run?", or asks to summarise or summarize ty ecosystem results for a Ruff PR from a PR number, PR URL, GitHub ecosystem-results comment, or detailed HTML report.