profile

Modify local settings files to enable or disable plugins for workflow profiles.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill profile-hiddink-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: profile
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/profile
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill profile-hiddink-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the overhead of managing large plugin sets by allowing users to switch between specialized workflow profiles, reducing the active plugin enumeration size and improving session focus.

Core Features & Use Cases

  • Plugin Set Switching: Dynamically enable or disable plugins based on specific development needs like web-app, data-eng, or harness-dev.
  • Session Optimization: Minimizes memory and context usage by loading only the necessary plugins for the current task.
  • Use Case: A developer switching from a data engineering task to a web application project can use this skill to instantly reconfigure their environment to load only relevant tools, avoiding clutter and potential conflicts.

Quick Start

Use the profile load command followed by the name of the profile you wish to activate to reconfigure your plugin set.

Frequently Asked Questions about profile

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

FAQPage Schema
How do I switch plugin configurations for different development workflows?

Switch plugin configurations by modifying local settings files within the .claude/ directory structure to match specific development workflow profiles. This dynamically enables or disables toolsets for targeted agent sessions.

How does loading a workflow profile optimize agent performance?

Loading a workflow profile optimizes agent performance by minimizing active plugin enumeration size and reducing memory usage. Only the necessary toolsets for the current task are loaded, improving session focus.

Why are shell scripts executed in the /tmp directory during configuration updates?

Shell scripts execute in the /tmp directory during configuration updates to safely bypass permission blocks. This ensures secure execution when modifying local settings files to match the desired workflow profile.

Can I instantly reconfigure my environment when moving from data engineering to web app development?

You can instantly reconfigure your environment by using the profile load command followed by the target profile name. This switches the active plugin set from data engineering tools to web application tools, avoiding clutter and conflicts.

What are the limitations of using workflow profiles for plugin set management?

Workflow profiles for plugin set management operate specifically within the .claude/ directory structure and require shell script execution via /tmp. If safe execution bypasses are blocked, configuration updates cannot proceed.

What is the best way to manage large plugin sets and reduce session overhead?

The best way to manage large plugin sets is switching between specialized workflow profiles. This reduces the active plugin enumeration size, minimizes context usage, and improves session focus for targeted development tasks.