'strings' 검색 결과

Guides edits to Worktrunk’s command-line messages, help text, and progress displays. Defines wording, colors, symbols, and where output goes, so command results and status messages follow consistent conventions in terminals, pipes, and redirected logs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Revising warning and error messages
• Separating command results from progress messages
• Checking color handling in redirected output

Write source files when direct file writing fails on quotes, backticks, or embedded variables in strings. The skill uses a temporary Python script executed through the shell and supports writing several files in one pass.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Save TypeScript files containing template literals
• Write scripts with mixed quotes and escape sequences
• Write several problematic files through one Python script

Write and review YARA-X rules, which identify malware through file patterns. Refine detection strings and conditions, check rule quality with included scripts, test against clean files, improve performance, and migrate rules from legacy YARA.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Write rules targeting a specific malware family
• Review false positives and slow detection rules
• Migrate existing YARA rules to YARA-X

Create dictionaries of keywords and identifying byte sequences for fuzzing, or testing with generated inputs. Extract useful entries from code, binaries, or specifications, then configure fuzzers to explore parsing paths beyond initial input validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a dictionary for JSON or XML parser fuzzing
• Add protocol keywords to generated test inputs
• Test image parsers with file signatures and chunk names

Generate README.md and DESIGN.md outlines by inspecting a module's files, language, and dependencies. Python analysis also extracts classes, functions, and docstrings, providing a starting point for usage documentation and design records that you complete afterward.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create documentation outlines for a new module
• Add missing README.md and DESIGN.md files
• Summarize Python classes and functions

Turn percentage strings into numeric data, calculate the remaining share needed to reach 100%, and create stacked bar charts. Compare category composition across periods or groups and save the chart as a high-resolution image.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Charting monthly changes in category shares
• Comparing composition across groups
• Calculating an Other category from remaining percentages

Scans .NET code for ~50 performance anti-patterns across async, memory, strings, collections, LINQ, regex, serialization, and I/O with tiered severity classification. Use when analyzing .NET code for optimization opportunities, reviewing hot paths, or auditing allocation-heavy patterns.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hunt server-side template injection (SSTI) across Jinja2 (Flask/Django), Twig (Symfony), Freemarker (Java), ERB (Rails), Spring, Velocity, Mako, Thymeleaf, Smarty. Detection probes use double-curly and dollar-curly math expressions evaluated server-side. Once an engine is fingerprinted, escalate to RCE via the engine-specific class-walker, callback-registrar, or Execute-utility patterns documented in disclosed reports. Detection patterns: error messages reveal engine, blank or numeric eval reveals expression mode. Targets: email templates, PDF/report generators, CMS preview features, error pages with user input. Use when hunting RCE via template rendering, when content shows engine fingerprints, when finding endpoints that compose strings with user input before render.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Searches and rewrites code by AST shape across 25 languages. Use when the target is a syntax pattern (every call/class/import shaped like X, a codemod, a YAML rule) rather than literal text; for plain strings, comments, or filenames, use rg.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals. Not for applying optimization patterns once profiling has identified a bottleneck (→ See `samber/cc-skills-golang@golang-performance` skill).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Provides binary exploitation techniques for CTF challenges. Use when you already have a vulnerable native target or service and need to turn memory corruption or low-level primitives into code execution or privilege escalation, such as buffer overflows, format strings, heap bugs, ROP, ret2libc, shellcode, kernel exploitation, seccomp bypass, sandbox escape, or Windows/Linux exploit chains. Do not use it when the main blocker is understanding what the binary does; use reverse engineering first. Do not use it for pure web bugs, disk or packet forensics, or standalone crypto/math challenges.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Fill missing i18n translations in the viewer source JSON. Run this after adding or modifying English or Chinese UI strings in claude_tap/viewer_i18n.json — it auto-translates to ja, ko, fr, ar, de, ru via OpenRouter.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when you want to look up, map, and search for short genetic variants (SNPs, indels) in NCBI's dbSNP database. Resolves between rsIDs, genomic coordinates in VCF format, and HGVS strings. For an rsID, returns variant type, gene associations, clinical significance, allele frequencies, and genomic coordinates (GRCh38).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Azure Key Vault Secrets Java SDK for secret management. Use when storing, retrieving, or managing passwords, API keys, connection strings, or other sensitive configuration data.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Update documentation across the repo after API changes. Finds stale references in docs, examples, docstrings, and fixes them.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write any link or URL so it resolves where it is rendered, not where it lives in the repo. Use when authoring or editing a link — in docs, source docstrings, READMEs (incl. npm-published), or product UI: docs cross-refs, "see SECURITY.md", universal `/_/` routes, GitHub URLs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Format string exploitation playbook. Use when printf-family functions receive user-controlled format strings, enabling arbitrary stack reads (%p/%s), arbitrary memory writes (%n/%hn/%hhn), GOT/hook overwrites, and canary/libc/PIE leaks.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Restore function symbols by analyzing code patterns, strings, constants, and cross-references

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.