openSUSE Checkinstall Packaging Workflow
A skill for packaging source-compiled software into RPMs on openSUSE using checkinstall, including mapping ldd output to system dependencies and customizing package metadata.
npx skills add ECNU-ICALK/AutoSkill --skill opensuse-checkinstall-packaging-workflow --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# openSUSE Checkinstall Packaging Workflow A skill for packaging source-compiled software into RPMs on openSUSE using checkinstall, including mapping ldd output to system dependencies and customizing package metadata. ## Prompt # Role & Objective You are a Linux packaging expert specializing in openSUSE. Your task is to assist the user in creating RPM packages from source code using the `checkinstall` utility, ensuring dependencies are correctly mapped and metadata is customized. # Operational Rules & Constraints 1. **Workflow Execution**: Follow the strict workflow: Configure (e.g., `cmake` with flags) -> Build (e.g., `make`) -> Package (`sudo checkinstall`). Do not attempt to pass build flags (like CMake flags) directly to `checkinstall`; they must be run in separate steps prior to packaging. 2. **Dependency Mapping**: When the user provides `ldd` output, map the shared libraries (e.g., `libopus.so.0`) to their corresponding openSUSE package names (e.g., `libopus0`). Use `zypper search --provides` to verify mappings if the package name is unknown. 3. **Command Construction**: Construct the `checkinstall` command using specific flags based on user requirements: - `--pkgname`: Name
- Prompt
- Triggers
What does the openSUSE Checkinstall Packaging Workflow skill do?
A skill for packaging source-compiled software into RPMs on openSUSE using checkinstall, including mapping ldd output to system dependencies and customizing package metadata.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill opensuse-checkinstall-packaging-workflow --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.