work — community quiver, community, ide skills

v1.0.0

About this Skill

Ideal for Data Engineering Agents requiring streamlined multi-source data integration with Apache Arrow. Execute an end-to-end GitHub issue workflow: select an issue, branch, implement with tests, validate, review, and open a PR. Use when asked to work on issue X or deliver a complete implementation work

fwojciec fwojciec
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
20
Canonical Locale
en
Detected Body Locale
en

Ideal for Data Engineering Agents requiring streamlined multi-source data integration with Apache Arrow. Execute an end-to-end GitHub issue workflow: select an issue, branch, implement with tests, validate, review, and open a PR. Use when asked to work on issue X or deliver a complete implementation work

Core Value

Enables agents to drive issue work from selection to PR with minimal back-and-forth using TDD methodology. It provides direct implementation of non-behavioral wiring/types and leverages Rust for reading data from BigQuery and PostgreSQL sources.

Ideal Agent Persona

Ideal for Data Engineering Agents requiring streamlined multi-source data integration with Apache Arrow.

Capabilities Granted for work

Automating data integration workflows
Implementing TDD for behavior changes
Streamlining PR creation from issue selection

! Prerequisites & Limits

  • Requires clean repo state on main branch
  • Depends on Apache Arrow infrastructure
  • Needs issue number input for branch creation

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is work?

Ideal for Data Engineering Agents requiring streamlined multi-source data integration with Apache Arrow. Execute an end-to-end GitHub issue workflow: select an issue, branch, implement with tests, validate, review, and open a PR. Use when asked to work on issue X or deliver a complete implementation work

How do I install work?

Run the command: npx killer-skills add fwojciec/quiver. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for work?

Key use cases include: Automating data integration workflows, Implementing TDD for behavior changes, Streamlining PR creation from issue selection.

Which IDEs are compatible with work?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for work?

Requires clean repo state on main branch. Depends on Apache Arrow infrastructure. Needs issue number input for branch creation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add fwojciec/quiver. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use work immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

work

Install work, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Work Issue End-to-End

Drive issue work from selection to PR with minimal back-and-forth.

Phase 1: Preflight + Selection

  1. Confirm repo is in a safe starting state (usually clean tree on main).
  2. If issue number is missing, list open issues and ask user to pick one.
  3. Fetch issue details (including comments) and create branch <number>-<kebab-title>.

Phase 2: Implement

  1. Prefer TDD for behavior changes (red/green/refactor).
  2. Implement non-behavioral wiring/types directly.
  3. Run make validate during development.
  4. Keep scope aligned with issue constraints.

Phase 3: Review

  1. Run code-review skill.
  2. Run review-with-gemini when available.
  3. Apply straightforward fixes automatically.
  4. If blocking feedback remains, pause and present options:
    • fix and re-review,
    • proceed with explicit override,
    • stop and document learnings.

Phase 4: Finalize

  1. Run full checks (make validate-full when available, else project equivalent).
  2. Commit cleanly.
  3. Push branch and open PR with summary + test plan + Closes #<issue>.
  4. Comment on issue with PR link and validation status.

Phase 5: Handoff

After PR creation, ask whether to:

  1. merge now,
  2. leave for user merge,
  3. keep iterating on branch.

Prefer ending in a clean local state on latest main unless user wants continued branch work.

Related Skills

Looking for an alternative to work or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer