Programming Assistant

Assist with programming tasks using Claude CLI. Use when OpenClaw needs to perform coding tasks, create new programs, modify existing code, or get programmin...

Security Scan

The skill's files and runtime instructions mainly match a programming helper that uses the Claude CLI, but there are small inconsistencies (notably a missing declared dependency on the 'claude' binary) and the included init script will create files and run git if available — review those before use.

Purpose & Capability

The SKILL.md explicitly requires Claude CLI (the 'claude' command) and references IDE integration, authentication, and using bash/Edit/Read tools, but the skill metadata lists no required binaries or primary credential. This omission is a coherence gap: a skill that depends on an external CLI should declare that dependency so callers and sandboxing can enforce it. Other than that omission, the provided scripts and docs align with the stated programming-assistant purpose.

Instruction Scope

The instructions direct the agent to read and write files in the target project directory, use the Claude CLI, run shell commands, and review/test generated code. These actions are within the stated purpose (project setup, code generation, editing, review). The SKILL.md does not instruct the agent to access unrelated system areas, exfiltrate data, or contact unknown external endpoints.

Install Mechanism

There is no install spec (instruction-only) and only one small helper script is included. No downloads, package installs, or extraction steps are present. This is the lower-risk model for skills.

Credentials

The skill declares no required environment variables or credentials, which is consistent with the included files. However, the runtime instructions mention that Claude CLI must be 'available and authenticated' — the skill does not declare how authentication should be supplied (env vars, config files, or interactive auth). Confirm how the Claude CLI will be authenticated before use; do not store credentials inside this skill.

Persistence & Privilege

The skill is not marked always:true and does not request system-wide configuration changes. The included script will create project directories and (if git is installed) run 'git init' and create a .gitignore — these are expected behaviors for a project-initialization helper but do perform filesystem changes in the target directory. The skill does not attempt to modify other skills or global agent settings.

What to consider before installing

This skill appears to be a straightforward Claude-CLI-based programming helper, but check a few things before installing or running it: - Ensure you have (and trust) the Claude CLI: SKILL.md expects the 'claude' command and authentication, but the skill metadata doesn't declare that dependency. Install and authenticate Claude CLI separately and verify how it stores credentials. - Review scripts/init_project.sh before running: it will create directories/files in whatever target path you pass and will run 'git init' if git is available. Run it in a sandbox or on a safe path first. - Confirm that you will not inadvertently provide sensitive credentials to the skill or to the Claude CLI session. The skill mentions authentication but does not define an auth mechanism; do not paste secrets into an automated session unless you understand where they go. - Because the skill can read/write repository files, consider running it with limited filesystem permissions or in a disposable environment if you are unsure. If you want higher assurance, ask the publisher to update the skill metadata to declare the 'claude' binary as a required dependency and to document exactly how authentication is expected to be provided.

Programming Assistant Skill

Overview

This skill enables OpenClaw to leverage Claude CLI for sophisticated programming tasks. It provides structured workflows for coding activities including project creation, code modification, debugging, and optimization.

When to Use This Skill

Use this skill when OpenClaw encounters tasks such as:

• Creating new programs or scripts
• Modifying existing code files
• Debugging code issues
• Refactoring code for better performance/readability
• Performing code reviews
• Setting up new projects or adding features
• Converting code between languages or formats
• Generating documentation for code

Prerequisites

• Claude CLI must be installed (claude command available)
• Claude desktop application should be accessible for IDE integration
• Sufficient permissions to read/write files in the target directory

Basic Usage Patterns

Pattern 1: Simple Code Generation

When tasked with creating new code:

1. Identify the target directory for the project
2. Use claude --ide to initiate the coding session
3. Provide specific instructions about the desired functionality
4. Review the generated code for correctness

Pattern 2: Code Modification

When modifying existing code:

1. Determine the files that need to be changed
2. Use claude --ide --add-dir <project-path> to focus on the specific project
3. Request specific changes while preserving existing functionality
4. Verify the changes meet requirements

Pattern 3: Project Setup

When setting up new projects:

1. Create the necessary directory structure
2. Generate initial configuration files
3. Set up basic file templates
4. Ensure dependencies are properly documented

Workflow Steps

1. Assessment

• Determine the scope of the programming task
• Identify the target directory and relevant files
• Assess complexity and potential challenges

2. Preparation

• Ensure Claude CLI is available and authenticated
• Prepare any necessary context about the codebase
• Gather requirements and constraints

3. Execution

• Use appropriate Claude CLI commands based on the task
• Monitor progress and intervene if needed
• Ensure code quality and adherence to requirements

4. Verification

• Review generated code for correctness
• Test functionality if possible
• Validate that requirements were met

Available Tools Integration

The skill integrates with Claude CLI tools:

• Bash: For running commands, tests, and system operations
• Edit: For modifying files directly
• Read: For reading files to understand context
• IDE Integration: For seamless code editing experience

Error Handling

• If Claude CLI is unavailable, suggest alternative approaches
• If authentication is required, guide through setup process
• For complex projects, break tasks into smaller manageable pieces
• When facing permission issues, suggest alternative approaches

Best Practices

1. Always consider security implications when generating code
2. Follow language-specific best practices and conventions
3. Include appropriate error handling in generated code
4. Add comments and documentation where appropriate
5. Ensure generated code is maintainable and readable