[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73BBEWKYXV1HW5P3CEFJDDB":3,"skill-same:01M73BBEWKYXV1HW5P3CEFJDDB":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M73BBEWKYXV1HW5P3CEFJDDB","bedtools-genomic-intervals",null,"Genomic interval ops on BED\u002FBAM\u002FGFF\u002FVCF. Find overlaps, merge intervals, compute coverage, extract FASTA, find nearest features. Core for ChIP-seq peak annotation, region filtering, genome arithmetic. Use tabix for indexed single-region queries; use deeptools for normalized bigWig coverage.","bg-szy\u002FTOP-SKILLS","bg-szy","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F106576190?v=4","01M73A4E8KPV67SFXRY8XZGNBX","ShuZhiyong","01M73A4E96MQ294MHM74TZBVQD",6,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fbedtools-genomic-intervals\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"bedtools-genomic-intervals\"\ndescription: \"Genomic interval ops on BED\u002FBAM\u002FGFF\u002FVCF. Find overlaps, merge intervals, compute coverage, extract FASTA, find nearest features. Core for ChIP-seq peak annotation, region filtering, genome arithmetic. Use tabix for indexed single-region queries; use deeptools for normalized bigWig coverage.\"\nlicense: \"GPL-2.0\"\n---\n\n# bedtools — Genomic Interval Analysis Toolkit\n\n## Overview\n\nbedtools is the standard toolkit for operating on genomic intervals in BED, BAM, GFF, and VCF formats. It solves the core problem of genome arithmetic: finding overlaps between feature sets, computing coverage, extracting sequences, merging adjacent regions, and annotating features with nearest neighbors. bedtools operates on sorted coordinate lists and runs at C speed, making it practical for whole-genome analyses.\n\n## When to Use\n\n- Intersecting ChIP-seq peaks with gene annotations to find promoter-overlapping peaks\n- Merging overlapping ATAC-seq peaks or called regions across replicates\n- Computing read coverage depth over target capture regions\n- Extracting FASTA sequences for motif discovery or primer design\n- Finding the nearest gene to each regulatory element or variant\n- Subtracting blacklist or repeat regions from peak calls\n- Expanding genomic intervals by fixed distance (promoter regions)\n- Use `tabix` instead for fast indexed queries of a single genomic region\n- For normalized coverage bigWig tracks, use `deeptools bamCoverage` instead\n- Use `mosdepth` instead for whole-genome per-base depth (10× faster)\n\n## Prerequisites\n\n- **Python packages**: None required (command-line only)\n- **Input requirements**: BED\u002FBAM\u002FGFF\u002FVCF files; FASTA reference for `getfasta`; genome file (chromosome sizes) for `slop`\u002F`flank`\u002F`genomecov`\n- **Sorting**: Most operations require coordinate-sorted input\n\n> **Check before installing**: The tool may already be available in the current environment (e.g., inside a `pixi` \u002F `conda` env). Run `command -v bedtools` first and skip the install commands below if it returns a path. When running inside a pixi project, invoke the tool via `pixi run bedtools` rather than bare `bedtools`.\n\n```bash\n# Bioconda (recommended)\nconda install -c bioconda bedtools\n\n# Homebrew (macOS)\nbrew install bedtools\n\n# Verify\nbedtools --version\n# bedtools v2.31.0\n\n# Create genome file from FASTA index\nsamtools faidx reference.fa\ncut -f1,2 reference.fa.fai > genome.txt  # chr → size table\n```\n\n## Pre-flight Interview\n\nSettle these with the user before writing any analysis code.\n\n```yaml\ndecisions:\n  - id: D1\n    param: overlapRequirement\n    kind: required\n    source: user\n    ask: \"How much of a feature must overlap before the two count as intersecting - a single base, or a stated fraction?\"\n    default: \"one base\"\n\n  - id: D2\n    param: reciprocalOverlap\n    kind: required\n    source: user\n    depends_on: [D1]\n    ask: \"Must the fraction hold for both features, or only for the query?\"\n    default: \"query only\"\n    skip_if: \"overlap requirement left at a single base\"\n\n  - id: D3\n    param: strandedness\n    kind: required\n    source: data\n    ask: \"Do the features carry strand, and must two features share it to be considered overlapping?\"\n    default: \"strand ignored\"\n\n  - id: D4\n    param: mergeDistance\n    kind: optional\n    source: user\n    ask: \"How close may two intervals be before they are merged into one?\"\n    default: \"touching or overlapping only\"\n\n  - id: D5\n    param: coverageScaling\n    kind: optional_conditional\n    source: upstream\n    ask: \"Should coverage be scaled to a per-million factor so samples are comparable?\"\n    default: \"raw coverage\"\n\n  - id: D6\n    param: sortedInput\n    kind: never_ask\n    source: data\n    reason: \"The sweep algorithm needs sorted input and changes memory and speed, not the intervals returned\"\n    default: \"used when inputs are sorted\"\n```\n\nD3 is the quiet one. For stranded features - genes, stranded RNA coverage,\nmotif hits - ignoring strand reports antisense overlaps as real, and the output\nis a perfectly ordinary BED file with too many rows.\n\n## Quick Start\n\n```bash\n# Find peaks overlapping genes, then merge overlapping peaks\nbedtools intersect -a peaks.bed -b genes.bed -wa -wb > peaks_with_genes.bed\nbedtools merge -i peaks.bed > merged_peaks.bed\nbedtools coverage -a genes.bed -b reads.bam > gene_coverage.bed\n```\n\n## Core API\n\n### Module 1: Interval Intersection and Overlap Analysis\n\nFind regions that overlap between two feature sets.\n\n```bash\n# Basic intersection: output overlapping regions\nbedtools intersect -a peaks.bed -b genes.bed\n\n# Report original A and B features for each overlap\nbedtools intersect -a peaks.bed -b genes.bed -wa -wb\n\n# Count B overlaps per A feature (adds column)\nbedtools intersect -a peaks.bed -b genes.bed -c\n# Output: chr1  1000  2000  peak1  gene_count\n\n# Peaks with ANY overlap (report each peak once)\nbedtools intersect -a peaks.bed -b genes.bed -u\n\n# Peaks with NO overlap in B (invert filter)\nbedtools intersect -a peaks.bed -b blacklist.bed -v\n```\n\n```bash\n# Require reciprocal 50% overlap both ways\nbedtools intersect -a exp1.bed -b exp2.bed -f 0.5 -F 0.5 -r\n\n# Same-strand intersections only\nbedtools intersect -a peaks.bed -b genes.bed -s\n\n# Multiple database files with overlap counts per file\nbedtools intersect -a query.bed -b enhancers.bed promoters.bed \\\n    -names enh prom -C\n\n# Memory-efficient mode for pre-sorted large files\nbedtools intersect -a sorted_peaks.bed -b sorted_genes.bed -sorted\n```\n\n### Module 2: Interval Merging and Arithmetic\n\nCombine overlapping intervals and perform set operations.\n\n```bash\n# Merge overlapping and adjacent intervals\nsort -k1,1 -k2,2n peaks.bed | bedtools merge -i stdin\n\n# Merge intervals within 500 bp of each other\nbedtools merge -i peaks.bed -d 500\n\n# Merge and count original features\nbedtools merge -i peaks.bed -c 1 -o count\n# Output: chr1  1000  5000  3 (3 original peaks merged)\n\n# Merge and collapse feature names\nbedtools merge -i peaks.bed -c 4 -o collapse -delim \";\"\n# Output: chr1  1000  5000  peak1;peak2;peak3\n```\n\n```bash\n# Subtract B from A (remove covered bases)\nbedtools subtract -a peaks.bed -b blacklist.bed\n\n# Remove entire A feature if ANY B overlap\nbedtools subtract -a peaks.bed -b exclusion.bed -A\n\n# Find genomic gaps (complement of covered regions)\nbedtools complement -i merged.bed -g genome.txt\n```\n\n### Module 3: Coverage Analysis\n\nCalculate depth and breadth of read coverage over features.\n\n```bash\n# Coverage stats per feature (count, bases covered, % covered)\nbedtools coverage -a target_genes.bed -b aligned.bam\n# Output: chr  start  end  gene  n_overlapping_reads  bases_covered  feature_len  fraction_covered\n\n# Per-base depth within each feature\nbedtools coverage -a targets.bed -b aligned.bam -d\n# Output: chr  start  end  name  position  depth\n\n# Coverage histogram per feature\nbedtools coverage -a features.bed -b aligned.bam -hist\n```\n\n```bash\n# Genome-wide BEDGRAPH (coverage per bin)\nbedtools genomecov -ibam aligned.bam -bg -o coverage.bedgraph\n\n# Include zero-coverage regions (for whole-genome coverage)\nbedtools genomecov -ibam aligned.bam -bga > full_coverage.bedgraph\n\n# Per-base depth for whole genome\nbedtools genomecov -ibam aligned.bam -d > depth.txt\n\n# Scaled BEDGRAPH (RPM normalization: total=50M reads → scale=1\u002F50)\nbedtools genomecov -ibam aligned.bam -bg -scale 0.00000002 > rpm.bedgraph\n\n# Strand-specific coverage tracks\nbedtools genomecov -ibam rnaseq.bam -bg -strand + > forward.bedgraph\nbedtools genomecov -ibam rnaseq.bam -bg -strand - > reverse.bedgraph\n```\n\n### Module 4: Sequence Extraction and Nearest Feature\n\nExtract genomic sequences and annotate features with neighbors.\n\n```bash\n# Extract FASTA sequences for each BED region\nbedtools getfasta -fi genome.fa -bed regions.bed -fo sequences.fasta\n\n# Strand-aware extraction (reverse complement - strand)\nbedtools getfasta -fi genome.fa -bed regions.bed -s -fo stranded.fasta\n\n# Custom FASTA headers (name + coords)\nbedtools getfasta -fi genome.fa -bed peaks.bed -name -fo named.fasta\n\n# Extract and concatenate exons (BED12 spliced transcripts)\nbedtools getfasta -fi genome.fa -bed transcripts.bed12 -split -fo exons.fasta\n```\n\n```bash\n# Find nearest gene to each peak (with distance)\nbedtools closest -a peaks.bed -b genes.bed -d\n# Output: peak fields... | gene fields... | distance_bp\n\n# Nearest feature on same strand only\nbedtools closest -a peaks.bed -b genes.bed -s -d\n\n# Ignore overlapping features (find nearest non-overlapping)\nbedtools closest -a peaks.bed -b genes.bed -io -d\n\n# Multiple annotation databases\nbedtools closest -a query.bed -b genes.bed enhancers.bed \\\n    -names genes enhancers -d\n```\n\n### Module 5: Interval Manipulation\n\nExpand, contract, and shift genomic intervals.\n\n```bash\n# Expand regions by 500 bp on each side\nbedtools slop -i peaks.bed -g genome.txt -b 500\n\n# Asymmetric: 2000 bp upstream, 500 bp downstream of TSS\nbedtools slop -i tss.bed -g genome.txt -l 2000 -r 500\n\n# Strand-aware expansion (upstream = 5' side)\nbedtools slop -i genes.bed -g genome.txt -l 1000 -r 200 -s\n\n# Create flanking regions (not overlapping the feature)\nbedtools flank -i genes.bed -g genome.txt -b 1000\nbedtools flank -i genes.bed -g genome.txt -l 2000 -r 0 -s  # upstream only\n```\n\n## Key Concepts\n\n### Coordinate Systems\n\nBED files use **0-based half-open** intervals: start is 0-indexed (like Python), end is exclusive. A region chr1:1000-2000 in BED covers bases 1000–1999 (1000 bases).\n\n```\nchr1  1000  2000  peak1   ← covers positions 1000,1001,...,1999\n# BED:  0-based start, exclusive end\n# VCF:  1-based position (POS)\n# GFF:  1-based start and end (both inclusive)\n```\n\nbedtools converts internally — input format is auto-detected. Problems arise when mixing tools with different conventions.\n\n### Sorting Requirements\n\nMost bedtools operations require **coordinate-sorted** input. Pre-sort with:\n\n```bash\nsort -k1,1 -k2,2n input.bed > sorted.bed\n# For large files, use -S 4G for 4 GB sort buffer\nsort -k1,1 -k2,2n -S 4G --parallel=8 input.bed > sorted.bed\n```\n\nThe `-sorted` flag in `bedtools intersect` uses a sweep algorithm that requires sorted input but uses O(1) memory instead of O(N).\n\n## Common Workflows\n\n### Workflow 1: ChIP-seq Peak Annotation\n\n**Goal**: Annotate peaks with overlapping genes, distances to TSS, and filter blacklisted regions.\n\n```bash\n#!\u002Fbin\u002Fbash\nPEAKS=\"peaks.bed\"\nGENES=\"refseq_genes.bed\"\nTSS=\"refseq_tss.bed\"       # BED with TSS positions\nBLACKLIST=\"encode_blacklist_hg38.bed\"\nGENOME=\"hg38.genome\"\n\n# 1. Remove blacklisted regions\nbedtools subtract -a $PEAKS -b $BLACKLIST -A > peaks_clean.bed\necho \"After blacklist filter: $(wc -l \u003C peaks_clean.bed) peaks\"\n\n# 2. Annotate with overlapping gene (allow 2 kb from gene body)\nbedtools slop -i $GENES -g $GENOME -b 2000 > genes_padded.bed\nbedtools intersect -a peaks_clean.bed -b genes_padded.bed -wa -wb \\\n    > peaks_gene_overlap.bed\n\n# 3. For non-overlapping peaks: find nearest gene\nbedtools intersect -a peaks_clean.bed -b genes_padded.bed -v > peaks_distal.bed\nbedtools closest -a peaks_distal.bed -b $TSS -d > peaks_distal_nearest.bed\n\necho \"Promoter peaks: $(wc -l \u003C peaks_gene_overlap.bed)\"\necho \"Distal peaks: $(wc -l \u003C peaks_distal.bed)\"\n```\n\n### Workflow 2: Coverage Analysis for WES Target Regions\n\n**Goal**: Calculate on-target read depth and coverage breadth for exome sequencing QC.\n\n```bash\n#!\u002Fbin\u002Fbash\nBAM=\"sample.deduped.bam\"\nTARGETS=\"capture_targets.bed\"\n\n# Per-target coverage statistics\nbedtools coverage -a $TARGETS -b $BAM > per_target_coverage.bed\n\n# Summary: total targets, mean depth, % at ≥20×\nawk 'BEGIN{n=0; depth=0; covered=0}\n     {n++; depth+=$7; if($8>=20) covered++}\n     END{printf \"Targets: %d\\nMean depth: %.1f×\\n%% at 20×: %.1f%%\\n\",\n         n, depth\u002Fn, covered\u002Fn*100}' per_target_coverage.bed\n\n# Per-base depth for IGV visualization\nbedtools coverage -a $TARGETS -b $BAM -d > per_base_depth.txt\necho \"Per-base depth written to per_base_depth.txt\"\n```\n\n## Key Parameters\n\n| Parameter | Command | Default | Range\u002FOptions | Effect |\n|-----------|---------|---------|---------------|--------|\n| `-f` | intersect, coverage | 1e-9 | 0.0–1.0 | Min fraction of A that must overlap |\n| `-F` | intersect, coverage | 1e-9 | 0.0–1.0 | Min fraction of B that must overlap |\n| `-r` | intersect | — | flag | Require reciprocal overlap (`-f` AND `-F`) |\n| `-s` | Most | — | flag | Strand-aware (same strand only) |\n| `-v` | intersect | — | flag | Report features with NO overlap (invert) |\n| `-c` | intersect | — | flag | Append overlap count per A feature |\n| `-d` | merge | 0 | integer | Max gap to merge (bp) |\n| `-bg` | genomecov | — | flag | BEDGRAPH output format |\n| `-scale` | genomecov | 1.0 | float | Multiply coverage by constant (for RPM) |\n| `-sorted` | intersect, closest | — | flag | Use sweep algorithm (sorted input required) |\n| `-b` | slop | — | integer | Expand interval by N bp on both sides |\n| `-D` | closest | — | ref\u002Fa\u002Fb | Report signed distance (upstream negative) |\n\n## Best Practices\n\n1. **Always sort before bedtools**: Most bedtools commands fail silently on unsorted input. Sort with `sort -k1,1 -k2,2n input.bed` before any bedtools operation.\n\n2. **Use `-sorted` for large files**: For pre-sorted files, `-sorted` reduces memory from O(N) to O(1). Required when intersecting multi-gigabyte BED files.\n\n3. **Check chromosome naming consistency**: The single most common failure — some tools use `chr1`, others use `1`. Verify with `cut -f1 file.bed | sort -u` before running intersections.\n\n4. **Apply blacklist early**: Run `bedtools subtract -b blacklist.bed -A` before any peak analysis. ENCODE blacklists remove artifactual signal in repetitive\u002Fhigh-copy regions.\n\n5. **Use `-f 0.5 -r` for peak reproducibility**: When intersecting peaks across replicates, require 50% reciprocal overlap to avoid spurious short overlaps at interval boundaries.\n\n6. **Validate BED format**: Malformed BED (wrong column count, text in numeric columns) causes silent failures. Test with `bedtools merge -i file.bed 2>&1 | head -5`.\n\n## Common Recipes\n\n### Recipe: Count Feature Overlaps Across Annotation Categories\n\n```bash\n# Report how many peaks overlap each category (genes, promoters, enhancers)\nfor category in genes.bed promoters.bed enhancers.bed repeats.bed; do\n    label=$(basename $category .bed)\n    count=$(bedtools intersect -a peaks.bed -b $category -u | wc -l)\n    total=$(wc -l \u003C peaks.bed)\n    echo \"$label: $count\u002F$total ($(echo \"scale=1; $count*100\u002F$total\" | bc)%)\"\ndone\n```\n\n### Recipe: Create Promoter Regions from Gene Annotations\n\n```bash\n# Extract 2kb upstream of TSS for ChIP annotation\n# For genes on + strand: TSS = start; on - strand: TSS = end\nawk 'BEGIN{OFS=\"\\t\"} $6==\"+\" {print $1,$2,$2+1,$4,$5,$6}\n                     $6==\"-\" {print $1,$3-1,$3,$4,$5,$6}' genes.bed > tss.bed\n\nbedtools slop -i tss.bed -g genome.txt -l 2000 -r 500 -s > promoters.bed\necho \"Created $(wc -l \u003C promoters.bed) promoter regions\"\n```\n\n### Recipe: Calculate Intersection Statistics\n\n```bash\n# Jaccard similarity between two peak sets (0=no overlap, 1=identical)\nbedtools sort -i set1.bed > s1.bed\nbedtools sort -i set2.bed > s2.bed\nbedtools jaccard -a s1.bed -b s2.bed\n# Output: intersection  union  jaccard  n_intersections\n#         423456        2345678  0.1804  892\n```\n\n## Troubleshooting\n\n| Problem | Cause | Solution |\n|---------|-------|----------|\n| Empty intersect output | Chromosome name mismatch (chr1 vs 1) | Check: `cut -f1 a.bed \\| sort -u` vs `cut -f1 b.bed \\| sort -u` |\n| Memory error on large files | Not using `-sorted` flag | Pre-sort inputs and add `-sorted` to intersect\u002Fclosest |\n| `getfasta: sequence not found` | FASTA headers differ from BED chr names | Index FASTA: `samtools faidx genome.fa`; match names exactly |\n| Zero coverage everywhere | BAM not indexed or BED\u002FBAM chr mismatch | Run `samtools index file.bam`; verify chr naming |\n| Merge doesn't merge expected features | Input not sorted by coordinate | Sort: `sort -k1,1 -k2,2n file.bed \\| bedtools merge -i stdin` |\n| `getfasta` produces wrong-strand sequence | Using `-s` without strand column in BED | Ensure BED col 6 has `+`\u002F`-`; add strand: `awk '{$6=\"+\"; print}' OFS=\"\\t\"` |\n| Off-by-one in coordinates | Mixing 0-based BED and 1-based VCF\u002FGFF | Convert GFF to BED: subtract 1 from start |\n| Slow on large genomes | Processing unsorted files | Sort both files; use `-sorted`; pipe through sort without writing temp files |\n\n## Related Skills\n\n- **samtools-bam-processing** — BAM sorting, filtering, and QC before passing to bedtools\n- **deeptools-ngs-analysis** — normalized coverage bigWig tracks and heatmaps from the BAM files bedtools processes\n- **pysam-genomic-files** — Python-native BAM\u002FBED manipulation for custom logic beyond bedtools\n\n## References\n\n- [bedtools documentation](https:\u002F\u002Fbedtools.readthedocs.io\u002F) — command reference and examples\n- [GitHub: arq5x\u002Fbedtools2](https:\u002F\u002Fgithub.com\u002Farq5x\u002Fbedtools2) — source, releases, issue tracker\n- Quinlan & Hall (2010) \"BEDTools: a flexible suite of utilities for comparing genomic features\" — [Bioinformatics 26(6)](https:\u002F\u002Fdoi.org\u002F10.1093\u002Fbioinformatics\u002Fbtq033)\n- [ENCODE blacklist regions](https:\u002F\u002Fgithub.com\u002FBoyle-Lab\u002FBlacklist) — curated problematic genomic regions\n","# bedtools — Genomic Interval Analysis Toolkit\n\n## Overview\n\nbedtools is the standard toolkit for operating on genomic intervals in BED, BAM, GFF, and VCF formats. It solves the core problem of genome arithmetic: finding overlaps between feature sets, computing coverage, extracting sequences, merging adjacent regions, and annotating features with nearest neighbors. bedtools operates on sorted coordinate lists and runs at C speed, making it practical for whole-genome analyses.\n\n## When to Use\n\n- Intersecting ChIP-seq peaks with gene annotations to find promoter-overlapping peaks\n- Merging overlapping ATAC-seq peaks or called regions across replicates\n- Computing read coverage depth over target capture regions\n- Extracting FASTA sequences for motif discovery or primer design\n- Finding the nearest gene to each regulatory element or variant\n- Subtracting blacklist or repeat regions from peak calls\n- Expanding genomic intervals by fixed distance (promoter regions)\n- Use `tabix` instead for fast indexed queries of a single genomic region\n- For normalized coverage bigWig tracks, use `deeptools bamCoverage` instead\n- Use `mosdepth` instead for whole-genome per-base depth (10× faster)\n\n## Prerequisites\n\n- **Python packages**: None required (command-line only)\n- **Input requirements**: BED\u002FBAM\u002FGFF\u002FVCF files; FASTA reference for `getfasta`; genome file (chromosome sizes) for `slop`\u002F`flank`\u002F`genomecov`\n- **Sorting**: Most operations require coordinate-sorted input\n\n> **Check before installing**: The tool may already be available in the current environment (e.g., inside a `pixi` \u002F `conda` env). Run `command -v bedtools` first and skip the install commands below if it returns a path. When running inside a pixi project, invoke the tool via `pixi run bedtools` rather than bare `bedtools`.\n\n```bash\n# Bioconda (recommended)\nconda install -c bioconda bedtools\n\n# Homebrew (macOS)\nbrew install bedtools\n\n# Verify\nbedtools --version\n# bedtools v2.31.0\n\n# Create genome file from FASTA index\nsamtools faidx reference.fa\ncut -f1,2 reference.fa.fai > genome.txt  # chr → size table\n```\n\n## Pre-flight Interview\n\nSettle these with the user before writing any analysis code.\n\n```yaml\ndecisions:\n  - id: D1\n    param: overlapRequirement\n    kind: required\n    source: user\n    ask: \"How much of a feature must overlap before the two count as intersecting - a single base, or a stated fraction?\"\n    default: \"one base\"\n\n  - id: D2\n    param: reciprocalOverlap\n    kind: required\n    source: user\n    depends_on: [D1]\n    ask: \"Must the fraction hold for both features, or only for the query?\"\n    default: \"query only\"\n    skip_if: \"overlap requirement left at a single base\"\n\n  - id: D3\n    param: strandedness\n    kind: required\n    source: data\n    ask: \"Do the features carry strand, and must two features share it to be considered overlapping?\"\n    default: \"strand ignored\"\n\n  - id: D4\n    param: mergeDistance\n    kind: optional\n    source: user\n    ask: \"How close may two intervals be before they are merged into one?\"\n    default: \"touching or overlapping only\"\n\n  - id: D5\n    param: coverageScaling\n    kind: optional_conditional\n    source: upstream\n    ask: \"Should coverage be scaled to a per-million factor so samples are comparable?\"\n    default: \"raw coverage\"\n\n  - id: D6\n    param: sortedInput\n    kind: never_ask\n    source: data\n    reason: \"The sweep algorithm needs sorted input and changes memory and speed, not the intervals returned\"\n    default: \"used when inputs are sorted\"\n```\n\nD3 is the quiet one. For stranded features - genes, stranded RNA coverage,\nmotif hits - ignoring strand reports antisense overlaps as real, and the output\nis a perfectly ordinary BED file with too many rows.\n\n## Quick Start\n\n```bash\n# Find peaks overlapping genes, then merge overlapping peaks\nbedtools intersect -a peaks.bed -b genes.bed -wa -wb > peaks_with_genes.bed\nbedtools merge -i peaks.bed > merged_peaks.bed\nbedtools coverage -a genes.bed -b reads.bam > gene_coverage.bed\n```\n\n## Core API\n\n### Module 1: Interval Intersection and Overlap Analysis\n\nFind regions that overlap between two feature sets.\n\n```bash\n# Basic intersection: output overlapping regions\nbedtools intersect -a peaks.bed -b genes.bed\n\n# Report original A and B features for each overlap\nbedtools intersect -a peaks.bed -b genes.bed -wa -wb\n\n# Count B overlaps per A feature (adds column)\nbedtools intersect -a peaks.bed -b genes.bed -c\n# Output: chr1  1000  2000  peak1  gene_count\n\n# Peaks with ANY overlap (report each peak once)\nbedtools intersect -a peaks.bed -b genes.bed -u\n\n# Peaks with NO overlap in B (invert filter)\nbedtools intersect -a peaks.bed -b blacklist.bed -v\n```\n\n```bash\n# Require reciprocal 50% overlap both ways\nbedtools intersect -a exp1.bed -b exp2.bed -f 0.5 -F 0.5 -r\n\n# Same-strand intersections only\nbedtools intersect -a peaks.bed -b genes.bed -s\n\n# Multiple database files with overlap counts per file\nbedtools intersect -a query.bed -b enhancers.bed promoters.bed \\\n    -names enh prom -C\n\n# Memory-efficient mode for pre-sorted large files\nbedtools intersect -a sorted_peaks.bed -b sorted_genes.bed -sorted\n```\n\n### Module 2: Interval Merging and Arithmetic\n\nCombine overlapping intervals and perform set operations.\n\n```bash\n# Merge overlapping and adjacent intervals\nsort -k1,1 -k2,2n peaks.bed | bedtools merge -i stdin\n\n# Merge intervals within 500 bp of each other\nbedtools merge -i peaks.bed -d 500\n\n# Merge and count original features\nbedtools merge -i peaks.bed -c 1 -o count\n# Output: chr1  1000  5000  3 (3 original peaks merged)\n\n# Merge and collapse feature names\nbedtools merge -i peaks.bed -c 4 -o collapse -delim \";\"\n# Output: chr1  1000  5000  peak1;peak2;peak3\n```\n\n```bash\n# Subtract B from A (remove covered bases)\nbedtools subtract -a peaks.bed -b blacklist.bed\n\n# Remove entire A feature if ANY B overlap\nbedtools subtract -a peaks.bed -b exclusion.bed -A\n\n# Find genomic gaps (complement of covered regions)\nbedtools complement -i merged.bed -g genome.txt\n```\n\n### Module 3: Coverage Analysis\n\nCalculate depth and breadth of read coverage over features.\n\n```bash\n# Coverage stats per feature (count, bases covered, % covered)\nbedtools coverage -a target_genes.bed -b aligned.bam\n# Output: chr  start  end  gene  n_overlapping_reads  bases_covered  feature_len  fraction_covered\n\n# Per-base depth within each feature\nbedtools coverage -a targets.bed -b aligned.bam -d\n# Output: chr  start  end  name  position  depth\n\n# Coverage histogram per feature\nbedtools coverage -a features.bed -b aligned.bam -hist\n```\n\n```bash\n# Genome-wide BEDGRAPH (coverage per bin)\nbedtools genomecov -ibam aligned.bam -bg -o coverage.bedgraph\n\n# Include zero-coverage regions (for whole-genome coverage)\nbedtools genomecov -ibam aligned.bam -bga > full_coverage.bedgraph\n\n# Per-base depth for whole genome\nbedtools genomecov -ibam aligned.bam -d > depth.txt\n\n# Scaled BEDGRAPH (RPM normalization: total=50M reads → scale=1\u002F50)\nbedtools genomecov -ibam aligned.bam -bg -scale 0.00000002 > rpm.bedgraph\n\n# Strand-specific coverage tracks\nbedtools genomecov -ibam rnaseq.bam -bg -strand + > forward.bedgraph\nbedtools genomecov -ibam rnaseq.bam -bg -strand - > reverse.bedgraph\n```\n\n### Module 4: Sequence Extraction and Nearest Feature\n\nExtract genomic sequences and annotate features with neighbors.\n\n```bash\n# Extract FASTA sequences for each BED region\nbedtools getfasta -fi genome.fa -bed regions.bed -fo sequences.fasta\n\n# Strand-aware extraction (reverse complement - strand)\nbedtools getfasta -fi genome.fa -bed regions.bed -s -fo stranded.fasta\n\n# Custom FASTA headers (name + coords)\nbedtools getfasta -fi genome.fa -bed peaks.bed -name -fo named.fasta\n\n# Extract and concatenate exons (BED12 spliced transcripts)\nbedtools getfasta -fi genome.fa -bed transcripts.bed12 -split -fo exons.fasta\n```\n\n```bash\n# Find nearest gene to each peak (with distance)\nbedtools closest -a peaks.bed -b genes.bed -d\n# Output: peak fields... | gene fields... | distance_bp\n\n# Nearest feature on same strand only\nbedtools closest -a peaks.bed -b genes.bed -s -d\n\n# Ignore overlapping features (find nearest non-overlapping)\nbedtools closest -a peaks.bed -b genes.bed -io -d\n\n# Multiple annotation databases\nbedtools closest -a query.bed -b genes.bed enhancers.bed \\\n    -names genes enhancers -d\n```\n\n### Module 5: Interval Manipulation\n\nExpand, contract, and shift genomic intervals.\n\n```bash\n# Expand regions by 500 bp on each side\nbedtools slop -i peaks.bed -g genome.txt -b 500\n\n# Asymmetric: 2000 bp upstream, 500 bp downstream of TSS\nbedtools slop -i tss.bed -g genome.txt -l 2000 -r 500\n\n# Strand-aware expansion (upstream = 5' side)\nbedtools slop -i genes.bed -g genome.txt -l 1000 -r 200 -s\n\n# Create flanking regions (not overlapping the feature)\nbedtools flank -i genes.bed -g genome.txt -b 1000\nbedtools flank -i genes.bed -g genome.txt -l 2000 -r 0 -s  # upstream only\n```\n\n## Key Concepts\n\n### Coordinate Systems\n\nBED files use **0-based half-open** intervals: start is 0-indexed (like Python), end is exclusive. A region chr1:1000-2000 in BED covers bases 1000–1999 (1000 bases).\n\n```\nchr1  1000  2000  peak1   ← covers positions 1000,1001,...,1999\n# BED:  0-based start, exclusive end\n# VCF:  1-based position (POS)\n# GFF:  1-based start and end (both inclusive)\n```\n\nbedtools converts internally — input format is auto-detected. Problems arise when mixing tools with different conventions.\n\n### Sorting Requirements\n\nMost bedtools operations require **coordinate-sorted** input. Pre-sort with:\n\n```bash\nsort -k1,1 -k2,2n input.bed > sorted.bed\n# For large files, use -S 4G for 4 GB sort buffer\nsort -k1,1 -k2,2n -S 4G --parallel=8 input.bed > sorted.bed\n```\n\nThe `-sorted` flag in `bedtools intersect` uses a sweep algorithm that requires sorted input but uses O(1) memory instead of O(N).\n\n## Common Workflows\n\n### Workflow 1: ChIP-seq Peak Annotation\n\n**Goal**: Annotate peaks with overlapping genes, distances to TSS, and filter blacklisted regions.\n\n```bash\n#!\u002Fbin\u002Fbash\nPEAKS=\"peaks.bed\"\nGENES=\"refseq_genes.bed\"\nTSS=\"refseq_tss.bed\"       # BED with TSS positions\nBLACKLIST=\"encode_blacklist_hg38.bed\"\nGENOME=\"hg38.genome\"\n\n# 1. Remove blacklisted regions\nbedtools subtract -a $PEAKS -b $BLACKLIST -A > peaks_clean.bed\necho \"After blacklist filter: $(wc -l \u003C peaks_clean.bed) peaks\"\n\n# 2. Annotate with overlapping gene (allow 2 kb from gene body)\nbedtools slop -i $GENES -g $GENOME -b 2000 > genes_padded.bed\nbedtools intersect -a peaks_clean.bed -b genes_padded.bed -wa -wb \\\n    > peaks_gene_overlap.bed\n\n# 3. For non-overlapping peaks: find nearest gene\nbedtools intersect -a peaks_clean.bed -b genes_padded.bed -v > peaks_distal.bed\nbedtools closest -a peaks_distal.bed -b $TSS -d > peaks_distal_nearest.bed\n\necho \"Promoter peaks: $(wc -l \u003C peaks_gene_overlap.bed)\"\necho \"Distal peaks: $(wc -l \u003C peaks_distal.bed)\"\n```\n\n### Workflow 2: Coverage Analysis for WES Target Regions\n\n**Goal**: Calculate on-target read depth and coverage breadth for exome sequencing QC.\n\n```bash\n#!\u002Fbin\u002Fbash\nBAM=\"sample.deduped.bam\"\nTARGETS=\"capture_targets.bed\"\n\n# Per-target coverage statistics\nbedtools coverage -a $TARGETS -b $BAM > per_target_coverage.bed\n\n# Summary: total targets, mean depth, % at ≥20×\nawk 'BEGIN{n=0; depth=0; covered=0}\n     {n++; depth+=$7; if($8>=20) covered++}\n     END{printf \"Targets: %d\\nMean depth: %.1f×\\n%% at 20×: %.1f%%\\n\",\n         n, depth\u002Fn, covered\u002Fn*100}' per_target_coverage.bed\n\n# Per-base depth for IGV visualization\nbedtools coverage -a $TARGETS -b $BAM -d > per_base_depth.txt\necho \"Per-base depth written to per_base_depth.txt\"\n```\n\n## Key Parameters\n\n| Parameter | Command | Default | Range\u002FOptions | Effect |\n|-----------|---------|---------|---------------|--------|\n| `-f` | intersect, coverage | 1e-9 | 0.0–1.0 | Min fraction of A that must overlap |\n| `-F` | intersect, coverage | 1e-9 | 0.0–1.0 | Min fraction of B that must overlap |\n| `-r` | intersect | — | flag | Require reciprocal overlap (`-f` AND `-F`) |\n| `-s` | Most | — | flag | Strand-aware (same strand only) |\n| `-v` | intersect | — | flag | Report features with NO overlap (invert) |\n| `-c` | intersect | — | flag | Append overlap count per A feature |\n| `-d` | merge | 0 | integer | Max gap to merge (bp) |\n| `-bg` | genomecov | — | flag | BEDGRAPH output format |\n| `-scale` | genomecov | 1.0 | float | Multiply coverage by constant (for RPM) |\n| `-sorted` | intersect, closest | — | flag | Use sweep algorithm (sorted input required) |\n| `-b` | slop | — | integer | Expand interval by N bp on both sides |\n| `-D` | closest | — | ref\u002Fa\u002Fb | Report signed distance (upstream negative) |\n\n## Best Practices\n\n1. **Always sort before bedtools**: Most bedtools commands fail silently on unsorted input. Sort with `sort -k1,1 -k2,2n input.bed` before any bedtools operation.\n\n2. **Use `-sorted` for large files**: For pre-sorted files, `-sorted` reduces memory from O(N) to O(1). Required when intersecting multi-gigabyte BED files.\n\n3. **Check chromosome naming consistency**: The single most common failure — some tools use `chr1`, others use `1`. Verify with `cut -f1 file.bed | sort -u` before running intersections.\n\n4. **Apply blacklist early**: Run `bedtools subtract -b blacklist.bed -A` before any peak analysis. ENCODE blacklists remove artifactual signal in repetitive\u002Fhigh-copy regions.\n\n5. **Use `-f 0.5 -r` for peak reproducibility**: When intersecting peaks across replicates, require 50% reciprocal overlap to avoid spurious short overlaps at interval boundaries.\n\n6. **Validate BED format**: Malformed BED (wrong column count, text in numeric columns) causes silent failures. Test with `bedtools merge -i file.bed 2>&1 | head -5`.\n\n## Common Recipes\n\n### Recipe: Count Feature Overlaps Across Annotation Categories\n\n```bash\n# Report how many peaks overlap each category (genes, promoters, enhancers)\nfor category in genes.bed promoters.bed enhancers.bed repeats.bed; do\n    label=$(basename $category .bed)\n    count=$(bedtools intersect -a peaks.bed -b $category -u | wc -l)\n    total=$(wc -l \u003C peaks.bed)\n    echo \"$label: $count\u002F$total ($(echo \"scale=1; $count*100\u002F$total\" | bc)%)\"\ndone\n```\n\n### Recipe: Create Promoter Regions from Gene Annotations\n\n```bash\n# Extract 2kb upstream of TSS for ChIP annotation\n# For genes on + strand: TSS = start; on - strand: TSS = end\nawk 'BEGIN{OFS=\"\\t\"} $6==\"+\" {print $1,$2,$2+1,$4,$5,$6}\n                     $6==\"-\" {print $1,$3-1,$3,$4,$5,$6}' genes.bed > tss.bed\n\nbedtools slop -i tss.bed -g genome.txt -l 2000 -r 500 -s > promoters.bed\necho \"Created $(wc -l \u003C promoters.bed) promoter regions\"\n```\n\n### Recipe: Calculate Intersection Statistics\n\n```bash\n# Jaccard similarity between two peak sets (0=no overlap, 1=identical)\nbedtools sort -i set1.bed > s1.bed\nbedtools sort -i set2.bed > s2.bed\nbedtools jaccard -a s1.bed -b s2.bed\n# Output: intersection  union  jaccard  n_intersections\n#         423456        2345678  0.1804  892\n```\n\n## Troubleshooting\n\n| Problem | Cause | Solution |\n|---------|-------|----------|\n| Empty intersect output | Chromosome name mismatch (chr1 vs 1) | Check: `cut -f1 a.bed \\| sort -u` vs `cut -f1 b.bed \\| sort -u` |\n| Memory error on large files | Not using `-sorted` flag | Pre-sort inputs and add `-sorted` to intersect\u002Fclosest |\n| `getfasta: sequence not found` | FASTA headers differ from BED chr names | Index FASTA: `samtools faidx genome.fa`; match names exactly |\n| Zero coverage everywhere | BAM not indexed or BED\u002FBAM chr mismatch | Run `samtools index file.bam`; verify chr naming |\n| Merge doesn't merge expected features | Input not sorted by coordinate | Sort: `sort -k1,1 -k2,2n file.bed \\| bedtools merge -i stdin` |\n| `getfasta` produces wrong-strand sequence | Using `-s` without strand column in BED | Ensure BED col 6 has `+`\u002F`-`; add strand: `awk '{$6=\"+\"; print}' OFS=\"\\t\"` |\n| Off-by-one in coordinates | Mixing 0-based BED and 1-based VCF\u002FGFF | Convert GFF to BED: subtract 1 from start |\n| Slow on large genomes | Processing unsorted files | Sort both files; use `-sorted`; pipe through sort without writing temp files |\n\n## Related Skills\n\n- **samtools-bam-processing** — BAM sorting, filtering, and QC before passing to bedtools\n- **deeptools-ngs-analysis** — normalized coverage bigWig tracks and heatmaps from the BAM files bedtools processes\n- **pysam-genomic-files** — Python-native BAM\u002FBED manipulation for custom logic beyond bedtools\n\n## References\n\n- [bedtools documentation](https:\u002F\u002Fbedtools.readthedocs.io\u002F) — command reference and examples\n- [GitHub: arq5x\u002Fbedtools2](https:\u002F\u002Fgithub.com\u002Farq5x\u002Fbedtools2) — source, releases, issue tracker\n- Quinlan & Hall (2010) \"BEDTools: a flexible suite of utilities for comparing genomic features\" — [Bioinformatics 26(6)](https:\u002F\u002Fdoi.org\u002F10.1093\u002Fbioinformatics\u002Fbtq033)\n- [ENCODE blacklist regions](https:\u002F\u002Fgithub.com\u002FBoyle-Lab\u002FBlacklist) — curated problematic genomic regions\n",{"name":5,"license":15,"description":7},"master","fd76f882a04e445e899d5cfb2732f2105ea054ee","skills\u002Fawesome-skills\u002Fbedtools-genomic-intervals",0,"https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS","https:\u002F\u002Fbg-szy.github.io\u002FTOP-SKILLS\u002F","https:\u002F\u002Fgithub.com\u002Fbg-szy","https:\u002F\u002Fwww.ecust.edu.cn\u002F","a student of East China University of Science and Technology","2026-11-15 03:38:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add bg-szy\u002FTOP-SKILLS --skill bedtools-genomic-intervals",{"tool":40,"command":41},"bunx","bunx skills add bg-szy\u002FTOP-SKILLS --skill bedtools-genomic-intervals",{"tool":43,"command":44},"pnpm","pnpm dlx skills add bg-szy\u002FTOP-SKILLS --skill bedtools-genomic-intervals","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fawesome-skills\u002Fbedtools-genomic-intervals\u002FSKILL.md",true,[],[49,58,65,72,79,86],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7DXW9N826PKXK174PVW3038","serpmaven","Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.","MIT","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fserpmaven\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":57},"01M7DXVHSTWDV65475QEQ915M7","revnu-landing-page-audit","Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: \"audit my landing page\", \"why isn't this page converting\", \"review my homepage\", \"my ads get clicks but no signups\", \"people bounce from the pricing page\", \"CRO review\", \"improve conversion rate\", \"is my hero section clear\", \"roast my landing page\", \"rewrite my headline\", \"what's wrong with this page\", \"landing page feedback\", \"make the signup page convert better\". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-landing-page-audit\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":57},"01M7DXV8X2D7B3VTD4HHYYHTGR","revnu-growth-context","Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents\u002Frevnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says \"set up our marketing context\", \"who is our ideal customer\", \"write our ICP\", \"describe the product for marketing\", \"positioning doc\", \"what's our brand voice\", \"remember this about our customers\", \"log what we tried\", \"what have we learned from marketing\", \"we changed pricing, update the context\", \"update our growth notes\", \"summarize the business for the agent\", \"import my product-marketing.md\", \"start a growth doc\", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-growth-context\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":57},"01M7DXV0DGJ1G0A60PAHC6J3C5","revnu-get-listed","Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: \"best X\" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says \"get us listed\", \"which directories should we submit to\", \"how do we get into best-of lists\", \"why does ChatGPT recommend competitors and not us\", \"get mentioned in AI answers\", \"submit to awesome lists\", \"get on G2\", \"where are our competitors listed\", \"pitch listicle authors\", \"find backlink opportunities\", \"launch directories\", \"get into roundups\", \"Product Hunt alternatives\", \"where should we be listed\", \"get cited by Perplexity\". Never submits, pays or posts without a yes. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-get-listed\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":57},"01M7DXTSPMGT9D6DSS0HP9BSTA","revnu-ai-readiness-audit","Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks \"is my site ready for AI search\", \"audit my site for AI answers\", \"AEO audit\", \"GEO audit\", \"why doesn't ChatGPT quote our pricing\", \"make our pages citable by AI\", \"do I need llms.txt\", \"does schema help with ChatGPT\", \"check our structured data\", \"is our content visible without JavaScript\", \"AI SEO audit\", \"optimize our homepage for AI answers\", \"LLM SEO check\", \"why does AI get our product wrong\", \"fix our site for AI Overviews\". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Frevnu-ai-readiness-audit\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":53,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":57},"01M7DXSZHCVTRS620GC3S97JZV","proxy-troubleshooting","Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.","https:\u002F\u002Fgithub.com\u002Fbg-szy\u002FTOP-SKILLS\u002Fblob\u002Fmaster\u002Fskills\u002Fmarketplace\u002Fproxy-troubleshooting\u002FSKILL.md",[],[]]