skills.rest
ShalomObongo
ShalomObongoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

add-parallel

A backward-compatibility layer that delegates Packfile reads and writes to lib-dmgr.

3|1|Updated Feb 10, 2026
Search Tags:#automation#compatibility#codex#skills#delegation#legacy#wrap
One-click install
npx skills add https://github.com/ShalomObongo/nanoclaw --skill add-parallel-shalomobongo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: add-parallel
Source: https://github.com/ShalomObongo/nanoclaw/tree/main/.claude/skills/add-parallel
Command: npx skills add https://github.com/ShalomObongo/nanoclaw --skill add-parallel-shalomobongo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy workflows and older automation relying on the add-parallel wrapper continue to function by delegating execution to the canonical skill, avoiding code duplication and breaking changes.

Core Features & Use Cases

  • Backward-compatibility delegation: routes to the canonical skill without introducing new logic.
  • Minimal upkeep: preserves behavior while allowing canonical updates to be centralized.
  • Use Case: In legacy automation, the wrapper ensures identical results to the canonical implementation.

Quick Start

Delegate to the canonical add-parallel skill to preserve backward compatibility.

Frequently Asked Questions about add-parallel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain backward compatibility for legacy automation skills?▼

To maintain backward compatibility for legacy automation skills, you can use a canonical wrapper that delegates execution to the updated skill, avoiding code duplication and breaking changes while preserving identical results.

When do I need a wrapper for legacy automation workflows?▼

You need a wrapper for legacy automation workflows when older references call a deprecated skill and must redirect execution to the canonical implementation to ensure consistent behavior without introducing new logic.

How do I delegate execution to a canonical skill SKILL.md?▼

To delegate execution to a canonical skill, implement a wrapper that routes older automation references directly to the canonical SKILL.md, ensuring centralized updates and identical results without duplicating logic.

Does a legacy wrapper skill introduce new processing logic?▼

No, a legacy wrapper skill does not introduce new processing logic. It strictly redirects execution to the canonical implementation to preserve behavior, allowing all updates to be centralized in one place.

What is the best way to avoid code duplication when updating legacy skills?▼

The best way to avoid code duplication when updating legacy skills is using a delegation wrapper that routes execution to a canonical implementation, centralizing updates while preserving backward compatibility for older workflows.

Why does my older automation reference still work after a skill update?▼

Your older automation reference still works because the legacy wrapper delegates execution to the canonical skill, ensuring consistent behavior and avoiding breaking changes while allowing centralized updates to the underlying logic.

Related Skills

Explore More Software Engineering Skills→
ShalomObongoShalomObongo
3

debug

Route legacy debug skill references to the canonical implementation.

Community
Basic
Lev0n82Lev0n82
1

mystery-novel-conventions

Plan mystery narratives with clue layouts and fair-play principles.

Community
Basic
ShalomObongoShalomObongo
3

customize

Redirect legacy skill calls to the canonical .codex/skills/customize/SKILL.md file.

Community
Basic
ShalomObongoShalomObongo
3

convert-to-docker

Delegate execution from legacy skill wrappers to the canonical convert-to-docker skill.

Community
Basic