SkillsAdd

vincentkoc/dotskills

crawlkit

Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.

First seen Jun 11, 2026

Installation

$ npx skills add vincentkoc/dotskills --skill crawlkit
View on skills.sh ↗ GitHub repository ↗

Also in this package

Other skills from vincentkoc/dotskills · top by installs.

npx skills add vincentkoc/dotskills
technical-documentation 219 technical-integrations 91 technical-deslop 88 technical-skill-finder 78 opik-optimizer 39 opik-integrations-auditor 36 semantic-slicing 27 openclaw-github-dedupe 25 operations-worktree 7 graincrawl 6

Browse all from vincentkoc/dotskills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 102
License LICENSE
Default branch main
Open issues 4
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
More metadata
source
https://github.com/vincentkoc/dotskills

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,547 B
  • docs SUMMARY.md 145 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Crawlkit

Purpose

Maintain crawlkit, the shared Go library for crawl app archive infrastructure. Use this skill to keep shared archive infrastructure reusable, tagged, and safe for downstream app branches.

When to use

  • Editing or reviewing crawlkit.
  • Moving common crawl app behavior into the library.
  • Checking whether gitcrawl, slacrawl, discrawl, or notcrawl can merge

against a released crawlkit tag.

  • Preparing or verifying a crawlkit Go module release.
  • Investigating shared TUI, snapshot, config, SQLite, mirror, progress, or

control metadata behavior.

Workflow

  1. Locate the crawlkit checkout from the current repository, an explicit user

path, or the configured workspace root.

  1. Read repo-local AGENTS.md, README.md, CONTRIBUTING.md, and

docs/publishing.md before release or compatibility work.

  1. Keep provider-specific logic out of crawlkit. Shared mechanics belong in

packages such as config, store, snapshot, mirror, state, output, progress, tui, cache, and control.

  1. Run the library gate with workspace masking disabled:

``bash GOWORK=off go mod tidy git diff --exit-code -- go.mod go.sum GOWORK=off go vet ./... GOWORK=off go test -count=1 ./... ``

  1. For release checks, verify the signed tag and public Go proxy:

``bash git tag -v <version> GOPROXY=https://proxy.golang.org GONOSUMDB= go list -m github.com/vincentkoc/crawlkit@<version> ``

  1. For downstream readiness, inspect app branches read-only. Confirm they are

clean, rebased, require the released crawlkit version, and pass:

``bash GOWORK=off go test ./... <app> --help <app> --version <app> metadata --json <app> status --json <app> tui --json ``

  1. Use temp HOME, XDGCONFIGHOME, and XDGCACHEHOME for CLI smokes.

Never mutate live app archives.

Inputs

  • Target task: library edit, release verification, downstream readiness, or TUI

backport.

  • Optional version tag such as v0.4.0.
  • Optional downstream app branch paths.

Outputs

  • A clean crawlkit change or readiness report.
  • Validation commands and results.
  • Explicit compatibility risks for downstream app branches.
  • Local binary rebuild notes only when the user asks for app binaries.