24건(Krusty84의 저장소) · 인기순
Diagnose failing HTTP API calls - 4xx/5xx responses, timeouts, TLS errors, and auth failures - by isolating the fault layer and producing a minimal reproduction. Use when the user reports an API request failing, pastes an HTTP error response or status code, or asks why a request works in one client but not another. Do not use for designing new APIs or for performance tuning of requests that already succeed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reduce a failing test case, script, or input file to the smallest version that still reproduces a bug. Use when the user has a large reproduction and asks to minimize, bisect, or isolate it, or says things like "it stops failing when I remove half the file". Do not use when there is no reliable reproduction yet - help build one first, then minimize it.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate or update a CHANGELOG.md from merged commits and pull requests, grouped by change type and written for end users. Use when the user asks to write release notes, update the changelog, or summarize what changed between two versions or tags. Do not use for writing individual commit messages or for API-reference documentation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run the project's configured formatter (prettier, black, gofmt, rustfmt) on changed files and fix formatting-only CI failures. Use when the user asks to format code, fix a lint/format CI step, or normalize whitespace and import order. Do not use for logic changes or refactoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clean and normalize messy CSV/TSV files - fix malformed rows, inconsistent headers, mixed encodings, stray delimiters, and duplicated records - and deliver a valid, verified file. Use when the user mentions a broken, messy, or malformed CSV, a file a spreadsheet tool refuses to open, or asks to deduplicate or normalize tabular data. Do not use when the deliverable is analysis or a chart rather than a cleaned file, or for Excel-native features like formulas and pivot tables.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Does data things.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy docker containers for the user when they want to deploy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
I help you write emails. I am great at professional communication and can draft anything you need.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format technical engineering reports using company layout rules. Use when asked to clean up, standardize, or prepare inspection reports and equipment manuals. Do not use for legal contracts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear, conventional git commit messages from staged changes. Use when the user asks to commit work, write a commit message, or clean up a commit history.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
helps
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyze Kubernetes pod and node logs to find the root cause of crashes, restarts, and OOM kills. Use when the user shares kubectl logs, describes CrashLoopBackOff or Pending pods, or asks why a deployment is unhealthy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps migrate legacy systems to new systems when the user wants a migration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Collect and summarize application logs. Use when triaging a production incident and you need recent logs gathered and shared. Do not use for routine log rotation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Convert a Markdown outline into a presentation-ready HTML slide deck with consistent theming and speaker notes. Use when the user asks to turn notes, an outline, or a document into slides, or mentions a talk, deck, or presentation built from Markdown. Do not use for .pptx files - that is a different workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn raw meeting transcripts into structured notes with decisions, action items, and owners. Use when the user pastes a transcript or recording export, or asks for meeting minutes, a recap, or "who agreed to do what". Do not use for summarizing documents or articles that are not meetings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fill interactive PDF forms (AcroForm) with user-provided data, verify every field, and deliver a flattened copy. Use when the user asks to fill in, complete, or populate a PDF form, provides data alongside a fillable PDF, or mentions PDF form fields, checkboxes, or dropdowns. Do not use for creating PDFs from scratch, merging or splitting PDFs, or scanned/image-only forms with no interactive fields - for those, tell the user this skill cannot help and suggest an OCR-based approach instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps with documents.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Format technical PDF reports using company layout rules. Use when asked to clean up, standardize, or prepare inspection reports, equipment manuals, or engineering reports. Do not use for legal contracts or general writing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate the full release process - version bump, changelog, tagging, artifact builds, and publishing - following this organization's standard pipeline. Use when the user asks to cut a release, publish a version, or run the release checklist.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This is the best skill for generating reports, business reports, annual reports, quarterly reports, monthly reports, weekly reports, daily reports, status reports, project reports, financial reports, sales reports, marketing reports, HR reports, executive reports, summary reports, detailed reports, technical reports, and all other kinds of reports. Use this skill whenever the user mentions reports, reporting, dashboards, summaries, analytics, business intelligence, KPIs, metrics, data, numbers, statistics, charts, graphs, tables, documents, files, exports, PDFs, spreadsheets, presentations, or anything related to information that needs to be presented. Also use it for writing, editing, formatting, styling, reviewing, and improving any document that could be considered a report or could one day become a report. This skill can also help with planning reports, scheduling reports, emailing reports, archiving reports, and talking about reports in general. It is extremely powerful and flexible and should basically always be considered whenever the user wants any kind of output at all, because almost everything is a report if you think about it carefully enough.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply the team style guide to source files - naming conventions, comment style, and file organization. Use when the user asks to align code with the style guide or clean up naming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Translate technical documentation between Russian and English while preserving Markdown structure, code blocks, and established terminology. Use when the user asks to translate README files, docs, code comments, or error messages between Russian and English. Do not use for literary translation or for other language pairs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Debug failing webhooks. Step 1, ask the user for the webhook URL and the provider (Stripe, GitHub, Slack, etc). Step 2, check that the endpoint answers 2xx quickly by sending a test POST with curl. Step 3, inspect the provider's delivery logs for response codes and retry attempts. Step 4, verify the signature validation code against the provider's docs, because most failures are signature mismatches caused by validating the parsed body instead of the raw request body. Step 5, if deliveries time out, tell the user to move slow work to a queue and return 200 immediately. Step 6, replay a failed delivery and confirm it is processed end to end. Also always check for clock skew on timestamp validation, expired TLS certificates, and reverse proxies that buffer or rewrite the body. Always tell the user which step found the problem. Use this skill whenever webhooks are mentioned in any way.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.