Does data things.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
So basically this skill is about data and you can use it for data related tasks like when there is data and something needs to happen with the data, for example transforming it or maybe looking at it, and the way you do this is you take the data and you process it, processing can mean different things depending on what the user wants which you should figure out somehow, also sometimes the data is in files and sometimes it is not in files, if it is in files you should open the files first obviously, and then do the processing we talked about earlier, oh and one more thing, if the data is big you should be careful because big data is harder than small data, everyone knows that, also this skill can help with databases too I guess since databases contain data, just connect to the database and get the data out and then it is basically the same as before, one thing I forgot to mention at the start is that you should always check the data first before doing anything, actually do that first, before all the other steps, and if anything goes wrong just try something else until it works, the user will tell you if it is wrong probably.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.