1.2천건 · 관련도순
act is an open-source CLI tool that runs GitHub Actions workflows locally using Docker, enabling fast feedback on workflow changes without pushing to GitHub. It is a standard tool for local Actions development and testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
AFFiNE is an open source workspace that combines docs, whiteboards, and lightweight databases in one product. This skill is useful when an agent needs to structure notes, maintain linked knowledge, or automate content workflows around AFFiNE workspaces and self-hosted deployments.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ActivityWatch is a privacy-first, open-source automated time tracker that records application usage, browser activity, and AFK status across Windows, macOS, and Linux. With 16k+ GitHub stars, it provides detailed productivity analytics without sending data to external servers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scaffold, build, and run MCP servers from a predictable Python project layout with tools, prompts, resources, auth, and OpenTelemetry hooks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Rates any SKILL.md on a 0-100 scale across 10 dimensions with a SHIP / REWORK / SCRAP verdict. Evaluates trigger precision, instruction clarity, output predictability, edge case coverage, anti-hallucination guardrails, developer experience, composability, open-source readiness, wow factor, and real-world utility. No flattery — calibrated against Anthropic's own skill-creator rubric. Use this skill whenever someone says "score this skill", "rate my skill", "is this skill good", "skill review", "skill audit", "roast my SKILL.md", "grade this", "will this skill work", "evaluate my skill", "how good is this", or pastes a SKILL.md and asks for feedback. Also trigger when comparing two skills, benchmarking a skill collection, or asking "what's wrong with this skill" — even without the word "score".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Post to Reddit using AppleScript Chrome control. Use when user wants to post to Reddit, share on subreddits, or promote open source projects on Reddit. Triggers on "post to reddit", "share on reddit", "reddit post", "submit to subreddit", or any Reddit posting request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `Meziantou.Analyzer` package for design, usage, security, performance, and style rules in .NET. Use when a repo wants broader analyzer coverage with a single NuGet package.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Set up or refine open-source .NET code-quality gates for CI: formatting, `.editorconfig`, SDK analyzers, third-party analyzers, coverage, mutation testing, architecture tests, and security scanning. Use when a .NET repo needs an explicit quality stack in `AGENTS.md`, docs, or pipeline YAML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Queries the NCATS Translator ARAX production API for bounded, typed, provenance-rich one-hop and endpoint-pinned two-hop biomedical knowledge-graph relationships. Use for Biolink-constrained RTX-KG2 lookup, explicit selected-provider ARAX federation, separate entity normalization, qualifier-aware graph traversal, and inspection of TRAPI edge bindings, publications, and knowledge-source provenance. Do not use for inference, ranking, open-ended pathfinding, clinical guidance, or sensitive queries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Find the most valuable commercial insight and the monetization point closest to lawful revenue for a project, product, service, website, community, content account, open-source tool, or business idea. Use when a user asks how to monetize, who pays, why people do not buy, what to charge, whether to keep building, what to stop, what to do next, or asks to continue or deepen an earlier business analysis. Answer the user's actual question before asking for more information and carry the analysis forward without repeating it. When the buyer, purchased result, or delivery ability is unknown, do not select them from industry stereotypes; use explicit conditional candidates and an evidence-gathering next step. Not for investment advice, income forecasts, get-rich-quick schemes, or guaranteed results.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Trademark filing procedures covering EUIPO (EU), USPTO (US), and WIPO Madrid Protocol (international). Walks through pre-filing conflict checks, Nice classification, descriptiveness assessment, mark type decisions, filing basis strategy, office-specific e-filing procedures, Madrid Protocol extension, post- filing monitoring, and open-source trademark policy drafting. Use after running screen-trademark to confirm the mark is clear, when ready to secure trademark rights in one or more jurisdictions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract maximum value from existing code — performance optimization, API surface refinement, and dead weight elimination. The art of turning base code into gold through systematic identification and amplification of value-bearing patterns. Use when optimizing a working but sluggish codebase, refining an API surface that has accumulated cruft, reducing bundle size or memory footprint, or preparing code for open-source release — when code works correctly but doesn't shine and needs polish rather than a full rewrite.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Polish screen recordings with Recordly (open-source Screen Studio alternative) — auto-zooms, cursor animations, webcam overlays, styled backgrounds, timeline editing. Also includes Slant: browser-based 3D perspective renderer with 12 animation presets and MP4/GIF export. Triggers on screen recording, demo video, Recordly, screen capture polish, product walkthrough, 3D perspective, Slant.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Vets whether to build a feature from scratch, use an existing free/open-source solution, or pay for a third-party API/service. Use this whenever the user asks Claude to implement, add, integrate, or write code for a feature or capability, especially one that sounds like it could already be a solved problem (auth, payments, scraping, animation, comment/DM automation, video/image generation, search, notifications, etc.), even if the user doesn't explicitly ask "should I build or buy this." Make sure to trigger this before writing non-trivial implementation code for any feature-level capability, not just when the user asks about libraries directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use before /plan-ceo-review or /plan-eng-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use only for user-provided academic text, explicit scholarly claims, existing citations, or known bibliographies needing citations added, verified, replaced, extracted, or formatted. Supports claim-to-source matching, citation-support checks, replacements, and common academic citation formats. Do not use for general fact-checking, legal/journalistic citation work, open-ended 'find literature about X', topic-level exhaustive discovery, systematic-review corpus construction, PRISMA searches, or creating new research claims. Chinese: 为已有段落补参考文献、核验已有引用、替换错误引用、提取需引文论断、GB/T 7714 格式化.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `Meziantou.Analyzer` package for design, usage, security, performance, and style rules in .NET. Use when a repo wants broader analyzer coverage with a single NuGet package.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `NetArchTest.Rules` library for architecture rules in .NET unit tests. Use when a repo wants lightweight, fluent architecture assertions for namespaces, dependencies, or layering.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.