2.1천건 · 관련도순
Define, validate, run, resume, and audit repo-local multi-step automations with current `asc workflow` and `.asc/workflow.json`, including step outputs and safe release/TestFlight workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market trends", or "state of the market". For chart-specific rank changes only, see market-movers. For keyword trends only, see keyword-research.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements. Use when asked to "update latest APIs", "refresh deprecated SwiftUI APIs", "check for new SwiftUI deprecations", "scan for API changes", or after a new iOS/Xcode release. Requires the Sosumi MCP to be available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run a 3-leg evaluation against a newly released LLM. Leg 1 is trap questions with deterministic answers, leg 2 is an agentic orchestration task with a planted failure, leg 3 is a brownfield feature build in a real repo. Use when the user wants to vibe-check, test, evaluate, or compare a new frontier model, or mentions model-bench, model vibe check, or launch-day protocol.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Read release notes/changelogs, update a defined dependency scope, handle breaking changes, and verify. Explicit-only; no broad update-everything by inference.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
GitHub via gh — issues, PRs, reviews, search, and CI runs. Use when: user mentions a repo, issue, PR, review, release, workflow run, or anything on github.com.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when acting as the orchestrator agent that drives Syntropic137 - running the dogfood loop, deciding what to dispatch next, landing agent PRs, deploying a beta, triaging failed executions, or keeping the scratchpad, paper cuts and retrospectives current. Trigger phrases include "orchestrator tick", "keep the loop running", "what should we dispatch next", "land these PRs", "why are PRs stacking up", "deploy the next beta", "pit stop", "the run failed, what now", "write the retro", "is the system helping", "scale quality", "learning loop for the orchestrator". Do NOT use for deciding whether one task belongs in a workspace or locally (see `dogfooding`), for turning one incident into an eval case (see `learning-loop`), for designing a workflow A/B experiment (see `workflow-experimentation`), or for release-branch and version-bump mechanics (see `devops`).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when deciding WHERE to do work on Syntropic137 itself - "run this through Syntropic", "dispatch a workflow", "should this go in a workspace or local", "kick off a run on the Mini", "dogfood this", "build Syntropic inside Syntropic", "why did the agent's push fail", "can an agent run our QA", "the execution says completed but nothing shipped". Covers what a workspace agent can and cannot do, why `.github/workflows` pushes must come from the local machine, how to write a task prompt that does not repeat a known failure, and how to verify a run actually delivered. Do NOT use for PR/release mechanics (see `devops`), for using the `syn` CLI as an end user (see the syntropic137 plugin skills), or for authoring workflow YAML.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate user-facing App Store release notes from git history since the last tag.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Secure Helm chart Dağıt:ments by validating chart integrity, scanning templates for misconfigurations, and enforcing security contexts in Kubernetes releases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
The NIST Cybersecurity Framework (CSF) 2.0, released in February 2024, provides a comprehensive taxonomy for managing cybersecurity risk through six core Functions - Govern, Identify, Protect, Detect, Respond, and Recover. bu skill covers conducting a maturity assessment against the CSF using Implementation Tiers to measure organizational cybersecurity posture and create improvement roadmaps.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clone/create/fork repos; manage remotes, releases.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze and optimize AGC (Automatic Gain Control) parameters for WaveCap-SDR channels. Use when audio is too quiet, too loud, has pumping artifacts, or when tuning AGC attack/release/target settings for FM/AM/SSB modes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates and maintains changelogs following Keep a Changelog format. Use when updating release notes, finishing tasks, or tagging versions. For version bumps, see semantic-versioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check the latest Claude (Anthropic), OpenAI Codex, and Google Gemini model releases from official primary sources, update model selections in this dotfiles repo, and update the Claude Code, Codex, and Gemini CLIs through their configured managers. Every run checks both the model settings and CLI for the selected provider, then scans the invoking repository for hardcoded model IDs. Use when the user asks to "モデル更新", "モデルを最新に", "最新モデル確認", "Codex/Claude Code/Gemini CLI本体の更新", "model bump", "update models", or "update agent CLIs". Do NOT use for one-off model selection in a single conversation, general model questions, or unrelated package updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
25 advanced engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, release management, platform ops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Safely update an npm package by checking npmjs.com for the latest version, reading release notes, and handling minor vs major upgrades differently. For minor updates, just do it. For major updates, find the upgrade guide, validate breaking changes, and produce a detailed migration report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install or update ToolUniverse in Claude Science — create the conda env, install the tooluniverse pip package, and (re)build the tooluniverse-research skill by fetching the current workflow library from GitHub. Use for first-time setup, upgrading the ToolUniverse version, refreshing the bundled workflows after an upstream release, or reinstalling on a new machine.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TOP PRIORITY skill — find and immediately fix or remove every piece of wrong, outdated, or redundant information in ToolUniverse docs. Wrong code, broken links, incorrect counts, and overlapping instructions must be fixed or removed — never left in place. Runs five phases: (D) static method scan, (C) live code execution, (A) automated validation, (B) ToolUniverse audit, (E) less-is-more simplification. Core philosophy: each concept appears exactly once; remove don't add; no emojis; single setup entry point. Use when reviewing docs, before releases, after API changes, or when asked to audit, fix, or simplify documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Add a standard AdwAboutDialog wired to app metadata, plus the AppStream metainfo file it should share data with. Use when adding an About entry, release notes, credits, or preparing app metadata.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.