New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

OpenLogi Device Fixture Contribution

by AprilNEA in AprilNEA/OpenLogi

Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.

Apache-2.0Auto-check passedTesting & QA

Install OpenLogi Device Fixture Contribution

skills CLI
$ npx skills add AprilNEA/OpenLogi --skill contributing-device-fixtures -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AprilNEA/OpenLogi contributing-device-fixtures --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AprilNEA/OpenLogi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/contributing-device-fixtures .claude/skills/contributing-device-fixtures && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
contributing-device-fixtures
GitHub stars
23k
Token cost
~1.2k tokens
SKILL.md length
591 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior.

  • Works in 4 steps: Read the fixture architecture and… → Choose a synthetic specimen ID and name;… → Identify one physical target and… → …
  • Recording a device profile or HID++ cassette for the OpenLogi fixture corpus
  • SKILL.md covers Prepare the capture, Capture through the existing…, Handle failures without losing… and Verify and review before sharing
  • Calls cargo

What it does

This skill guides contributors through recording a hardware fixture for OpenLogi, an open-source alternative to Logitech Options+, then checking it for privacy and verifying it offline. Preparation covers reading the fixture architecture doc, choosing a synthetic specimen ID and name with no serial numbers or contributor identity, using a fresh output folder named after the ID, and fixing one physical device and route for both capture phases.

Capture runs through the `openlogi fixture contribute` wizard. The first phase reads device state through the agent, and `--profile-only` stops there. Raw HID++ capture needs the matching agent and any competing hardware clients stopped first, and locks must never be deleted or bypassed. The session must not be described as zero-write, because it records eight named read operations and may enable notifications during discovery. The wizard is preferred over hand-built manifests, and on macOS a separate permission skill is loaded. The excerpt is cut off before the verification details.

When your agent uses it

  • Recording a device profile or HID++ cassette for the OpenLogi fixture corpus
  • Checking a fixture for serial numbers or personal identity before contributing it
  • Reviewing a pull request that changes the fixture corpus

Example prompts

  • “Record a fixture for my MX Master 3S using profile-only capture.”
  • “Walk me through contributing a device fixture and make sure it contains no serial numbers.”
  • “Review this fixture PR for privacy leaks and verify it offline.”

Requirements

  • The OpenLogi CLI, or a repository checkout to run it with cargo
  • A physical Logitech device and a compatible running OpenLogi agent

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read the fixture architecture and recording workflow.
  2. Choose a synthetic specimen ID and name; do not embed serials or contributor
  3. Identify one physical target and transport. --device accepts a case-insensitive
  4. Match the CLI's OPENLOGI_PROFILE to the agent that owns the target. Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit 0f69d75. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

OpenLogi Device Fixture Contribution loads about 1.2k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 591 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AprilNEA/OpenLogi at commit 0f69d75, republished under its Apache-2.0 licence (© AprilNEA). 591 words, ~1,238 tokens.

Download SKILL.mdSave it as .claude/skills/contributing-device-fixtures/SKILL.md (or your agent's skills folder).
name
contributing-device-fixtures
description
Guides OpenLogi device-fixture capture, privacy review, and offline verification with fixture contribute and verify. Use when recording device profiles or HID++ cassettes, contributing hardware fixtures, or reviewing fixture corpus changes.

Contribute Device Fixtures

Produce a sanitized, verifiable fixture without treating replay as proof of hardware correctness.

Prepare the capture

  1. Read the fixture architecture and recording workflow. Check current CLI support before using proposed features from that design doc. Use the repository CLI with cargo run -p openlogi -- <arguments> if the installed openlogi lacks the fixture commands.
  2. Choose a synthetic specimen ID and name; do not embed serials or contributor identity. Use a new output directory whose basename equals --id.
  3. Identify one physical target and transport. --device accepts a case-insensitive exact display name or exact rendered route; ambiguous selection must fail. Keep the same physical device and route for both phases.
  4. Match the CLI's OPENLOGI_PROFILE to the agent that owns the target. Confirm permission to interrupt the user's agent/apps and perform direct capture before entering the raw phase. Use --profile-only when direct capture is not authorized. Load the macOS permission skill on macOS; an agent grant does not authorize direct CLI access.

Capture through the existing wizard

With a compatible real agent running, use this command with the selected values:

sh
openlogi fixture contribute \
  --id mx-master-3s-001 \
  --name "MX Master 3S" \
  --device "MX Master 3S" \
  --output fixtures/devices/mx-master-3s-001
  • Phase one reads semantic state through the agent; there is no direct fallback. Check that it is the real target's snapshot, not the mock agent's inventory. --profile-only finishes here; raw-HID standalone devices also use that mode.
  • For HID++ raw capture, stop the matching agent and competing hardware clients, then rerun the same command. Inspect other profiles too: agent.lock protects only its own profile, and does not exclude Options+ or other direct diagnostics.
  • Let the recorder hold agent.lock and reject an active or unhealthy IPC endpoint. Do not delete locks, bypass ownership checks, or change profiles to evade them.
  • The current wizard records eight named read operations. Discovery can first enable receiver notifications and request arrival reports; flags are not restored. Do not describe the session as zero-write. Do not add setting writes or pairing.
  • Prefer the wizard over hand-built manifests. Use lower-level fixture record commands only for a focused case after reading their current --help and implementation.
Show full SKILL.md (251 more words)Show less

Handle failures without losing evidence

Read publication and resume behavior before recovering a failed capture. Files are published individually, not as one atomic directory. Publication errors can leave a partial case set; the resume state is removed before final on-disk verification.

  • If capture stops before publication, preserve the saved profile and resume state. After resolving the cause, rerun with the same metadata and physical target.
  • If publication or final verification fails, inspect the directory and error first. Do not promise automatic resume, delete existing output, or add --force blindly. The contribution wizard has no --force; lower-level record commands can replace files.
  • Refuse ambiguous routes, unclassified sensitive reports, ownership conflicts, and interrupted captures. Do not weaken sanitization or fabricate a successful case.

Verify and review before sharing

sh
openlogi fixture verify fixtures/devices/mx-master-3s-001
cargo test -p openlogi-cli fixture::verify

Require schema, privacy, relationship, and replay checks to pass. Strict verification accepts only the declared manifest, profile, and case files; exclude logs and resume state from the final fixture. These checks are offline and do not access hardware.

Review the model, transport, capabilities, and expected values against independent device evidence. Inspect sanitized JSON before sharing; do not persist raw identities, pairing secrets, host paths, or hashes of private identifiers. Do not regenerate expectations from replay output merely to make verification pass.

Report capture mode, CLI/agent versions, transport, verification results, and remaining semantic or hardware uncertainty. Record limitations outside the strict fixture directory. Restore only the processes stopped for the authorized capture. Do not upload, commit, or open a PR unless the task authorizes that action.

© AprilNEA, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/contributing-device-fixtures of AprilNEA/OpenLogi.

Open the folder on GitHubat commit 0f69d75

Compare with similar skills

OpenLogi Device Fixture Contribution next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

OpenLogi Device Fixture Contribution compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
OpenLogi Device Fixture Contribution this skillAprilNEA/OpenLogi23k—~1.2kAutomated safety check: PassApache-2.0
Apple Container Test RunnerRustPython/RustPython22k—~467Automated safety check: PassMIT
RTK Filter TDD in Rustrtk-ai/rtk83k—~1.9kAutomated safety check: NotesApache-2.0
Helper Visibilitypdparchitect/noodle160—~267Automated safety check: PassApache-2.0
Installer RigFreakStudioCN/mpy-hardware-extension154—~4.5kAutomated safety check: PassCustom licence
Testing Strategiesancoleman/ai-design-components525—~3.8kAutomated safety check: PassMIT

Similar skills

  • Apple Container Test Runner

    RustPython/RustPython

    Runs RustPython tests inside a Linux container built with Apple's container CLI, so macOS users can compare Linux results with their local ones.

    22k GitHub stars~467 tokensUpdated today
    Testing & QAAuto-check passed

  • RTK Filter TDD in Rust

    rtk-ai/rtk

    Enforces red-green-refactor for new RTK output filters in Rust, using real captured fixtures, snapshot tests with insta and token-savings assertions.

    83k GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes

  • Helper Visibility

    pdparchitect/noodle

    Dock and app-switcher policy for Noodle helpers. An agent skill from pdparchitect/noodle.

    160 GitHub stars~267 tokensUpdated today
    Testing & QAAuto-check passed

  • Installer Rig

    FreakStudioCN/mpy-hardware-extension

    Build, gate and acceptance-test the Rust installer (blockless-installer) on macOS and Windows.

    154 GitHub stars~4.5k tokensUpdated 12 days ago
    Testing & QAAuto-check passed

  • Testing Strategies

    ancoleman/ai-design-components

    Strategic guidance for choosing and implementing testing approaches across the test pyramid.

    525 GitHub stars~3.8k tokensUpdated 10 mo ago
    Testing & QAAuto-check passed

  • Use Test Fixtures

    0xMiden/protocol

    A skill your agent uses when a Rust or MASM test needs to construct an account, note, transaction, or other domain object — build it with the existing test fixtures.

    133 GitHub stars~377 tokensUpdated yesterday
    Testing & QAAuto-check passed

More from AprilNEA/OpenLogi

  • OpenLogi macOS Permissions Triage

    AprilNEA/OpenLogi

    Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.

    23k GitHub stars~2.5k tokensUpdated today
    Auto-check: notes

  • Testing OpenLogi UI

    AprilNEA/OpenLogi

    Verifies OpenLogi's native GPUI interface with focused tests, the component gallery and a mock agent, choosing the evidence that fits each change.

    23k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • OpenLogi Change Verification

    AprilNEA/OpenLogi

    Plans the smallest check that could disprove a code change in the OpenLogi project, then escalates through reproduction, focused tests and a final gate before a push.

    23k GitHub stars~1.4k tokensUpdated today
    Auto-check passed

  • OpenLogi Device Diagnosis

    AprilNEA/OpenLogi

    Finds the first failing layer when an OpenLogi Logitech device is missing or misbehaving across enumeration, open, probe, IPC and UI.

    23k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about OpenLogi Device Fixture Contribution

What does OpenLogi Device Fixture Contribution do?

Guides recording, privacy review and offline verification of OpenLogi device fixtures with the fixture contribute and verify commands, without treating replay as proof of hardware behavior. This skill guides contributors through recording a hardware fixture for OpenLogi, an open-source alternative to Logitech Options+, then checking it for privacy and verifying it offline. Preparation covers reading the fixture architecture doc, choosing a synthetic specimen ID and name with no serial numbers or contributor identity, using a fresh output folder named after the ID, and fixing one physical device and route for both capture phases.

When should I use OpenLogi Device Fixture Contribution?

OpenLogi Device Fixture Contribution fits situations like: recording a device profile or HID++ cassette for the OpenLogi fixture corpus; checking a fixture for serial numbers or personal identity before contributing it; reviewing a pull request that changes the fixture corpus.

How do I install OpenLogi Device Fixture Contribution in Claude Code?

Run `npx skills add AprilNEA/OpenLogi --skill contributing-device-fixtures -a claude-code`. Or copy the skill folder (.agents/skills/contributing-device-fixtures in AprilNEA/OpenLogi) into .claude/skills/contributing-device-fixtures in your project. Claude Code loads it when a task matches its description.

How do I install OpenLogi Device Fixture Contribution in Codex?

Run `npx skills add AprilNEA/OpenLogi --skill contributing-device-fixtures -a codex`. Or copy the skill folder (.agents/skills/contributing-device-fixtures in AprilNEA/OpenLogi) into .agents/skills/contributing-device-fixtures in your project. Codex loads it when a task matches its description.

Can I use OpenLogi Device Fixture Contribution in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AprilNEA/OpenLogi --skill contributing-device-fixtures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contributing-device-fixtures, .gemini/skills/contributing-device-fixtures, .github/skills/contributing-device-fixtures and .opencode/skills/contributing-device-fixtures in your project.

What does OpenLogi Device Fixture Contribution need to run?

Going by SKILL.md and its folder, OpenLogi Device Fixture Contribution needs the command-line tools its instructions call (cargo). Our summary lists: The OpenLogi CLI, or a repository checkout to run it with cargo; A physical Logitech device and a compatible running OpenLogi agent.

Does OpenLogi Device Fixture Contribution access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is OpenLogi Device Fixture Contribution safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does OpenLogi Device Fixture Contribution use?

OpenLogi Device Fixture Contribution is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does OpenLogi Device Fixture Contribution use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to OpenLogi Device Fixture Contribution?

Skills that share tags, products or a category with OpenLogi Device Fixture Contribution: Apple Container Test Runner (RustPython/RustPython, 22k stars), RTK Filter TDD in Rust (rtk-ai/rtk, 83k stars), Helper Visibility (pdparchitect/noodle, 160 stars) and Installer Rig (FreakStudioCN/mpy-hardware-extension, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains OpenLogi Device Fixture Contribution?

AprilNEA (a GitHub user) maintains it in AprilNEA/OpenLogi, which has 23,344 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 10, 2026.

Source: AprilNEA/OpenLogi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.