Working Dir Test Skill

Execute a local skill from working_dir/skills using SKILL.md frontmatter.

Updated Mar 27, 2022
One-click install
npx skills add https://github.com/emliunix/home.conf --skill working-dir-test-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Working Dir Test Skill
Source: https://github.com/emliunix/home.conf/tree/main/tskill/tests/fixtures/test_both_exist_repo/working_dir/skills/test_skill
Command: npx skills add https://github.com/emliunix/home.conf --skill working-dir-test-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local skill execution in the working directory eliminates reliance on centralized registries, speeding up development and testing.

Core Features & Use Cases

  • Self-contained execution: run the skill from working_dir/skills without external lookups.
  • Isolated testing: validate behavior in your project environment.
  • Use Case: A developer wants to verify a small automation directly in their repo before broader integration.

Quick Start

Run the skill from its local working directory to validate its behavior.

Frequently Asked Questions about Working Dir Test Skill

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

FAQPage Schema
How do I run local skills directly from my project's working directory?

Run local skills by executing them directly from the project's working_dir/skills folder, enabling isolated testing without external lookups. This requires a SKILL.md file with name and description frontmatter.

What is local skill execution in a development workflow?

Local skill execution runs self-contained automation from your working directory, eliminating reliance on centralized registries to speed up development and validate behavior in your project environment.

Do I need a centralized registry to test automation skills in my repo?

No, centralized registries are not needed. Local skill execution operates self-contained from the working_dir/skills directory, allowing you to verify automations directly in your repository before broader integration.

What file structure is required for executing a local skill from the working directory?

Executing a local skill requires a SKILL.md file containing name and description frontmatter. You can also include optional folders such as scripts, references, and assets to support the skill's activation and behavior.

When should I use working directory skill execution instead of external lookups?

Use working directory skill execution when you need isolated testing to validate a small automation directly in your repository environment before broader integration, eliminating external lookup dependencies.

Can I validate skill behavior in my project environment without external dependencies?

Yes, you can validate behavior in your project environment through self-contained execution. The skill runs directly from working_dir/skills, ensuring isolated testing without requiring external lookups or dependencies.