agentsclimarketplace

Author yara x rules

Skill gaelic-ghost/socket/skills/author-yara-x-rules

Author, test, tune, and document YARA-X rules from validated artifact evidence. Use when suspicious files, scripts, documents, or binary features need local detection with stable patterns, fixtures, performance checks, and regression tests.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill author-yara-x-rules

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, as published. Nobody here has run it

Author YARA-X Rules

Overview

Create rules that detect the validated property the evidence supports, not a broader malware-family claim. Prefer structural combinations over unique-looking strings copied from one sample.

Read references/yara-x-rule-quality.md before selecting patterns or declaring coverage.

Workflow

  1. Define the detection objective and non-goals.
  2. Build the fixture set.
    • Preserve representative positive samples and near-miss benign negatives with hashes and provenance.
    • Use synthetic or redistributable fixtures for repository tests.
  3. Select discriminators.
    • Prefer format/module facts, byte structures, stable code/config fragments, and combinations of independently meaningful strings.
    • Avoid mutable infrastructure, compiler boilerplate, paths, timestamps, or one generic API name as decisive evidence.
  4. Author metadata and conditions.
    • Include purpose, author, date, source/evidence reference, scope, confidence, and known limitations.
    • Bound file type and size where it improves correctness or performance.
  5. Validate with current YARA-X.
    • Record version; compile/lint the rule; test all positives, negatives, malformed inputs, and a bounded benign corpus.
    • Investigate timeouts, warnings, and module-undefined behavior.
  6. Review false positives and coverage.
    • Tune by improving evidence combinations, not by accumulating arbitrary exclusions.
  7. Preserve regression evidence.
    • Store allowed fixtures or deterministic generators, expected matches/non-matches, and rule revision.

Output

Return the rule, objective, evidence basis, fixture results, performance notes, known misses/false positives, and deployment limits.

What ships with it: 2 files

912 B alongside SKILL.md

agents/

references/

Gives 0 of the 12 instructions most test skills give

Counted across 1,201 of the 2,096 authors here whose files we hold, read 2026-09-06

  • Write a failing test before writing codein 43 of 1201, across 36 files
  • Run the full test suitein 36 of 1201, across 35 files
  • Test only one variable per experimentin 34 of 1201, across 17 files
  • Read product marketing context before asking questionsin 34 of 1201, across 14 files
  • Mock external dependenciesin 34 of 1201, across 30 files
  • Define primary, secondary, and guardrail metricsin 33 of 1201, across 16 files
  • Pre-determine sample size before startingin 31 of 1201, across 14 files
  • Test behavior rather than implementationin 31 of 1201, across 29 files
  • Formulate a hypothesis before designing a testin 30 of 1201, across 13 files
  • Document every test hypothesis, variant, and resultin 29 of 1201, across 11 files
  • Use descriptive test function namesin 25 of 1201, across 21 files
  • Commit to the methodology without stopping earlyin 24 of 1201, across 8 files

Said here and by no other author read

  • Define detection objectives and non-goals
  • Build a fixture set of positive and negative samples
  • Prefer structural combinations over unique strings
  • Include metadata and conditions in the rule
  • Validate rules with the YARA-X compiler
  • Test against positives and negatives

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 612,213. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.