using-agent-skills

Route development tasks to matching engineering workflow skills via SKILL.md metadata.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/logo-solutions/NAS-logo --skill using-agent-skills-logo-solutions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-agent-skills
Source: https://github.com/logo-solutions/NAS-logo/tree/main/skills/using-agent-skills
Command: npx skills add https://github.com/logo-solutions/NAS-logo --skill using-agent-skills-logo-solutions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This meta-skill solves the problem of choosing the correct engineering workflow and operational rules for any development task, preventing misapplied processes and missed verification steps.

Core Features & Use Cases

  • Skill Discovery: Identify the most appropriate skill for a task by mapping intent to named skills (e.g., idea-refine, spec-driven-development, test-driven-development).
  • Invocation Guidance: Load the selected skill's operating behaviors, verification steps, and failure-mode checks before execution.
  • Governance & Safety: Enforce core behaviors like surfacing assumptions, managing confusion, and requiring verification before marking work done.
  • Use Case: When given a feature request or bug report, determine whether to start with spec-driven-development, debugging-and-error-recovery, or an incremental-implementation slice and apply the corresponding verification rules.

Quick Start

Ask the agent to identify and apply the correct skill for the current task, then follow its verification checklist.

Frequently Asked Questions about using-agent-skills

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

FAQPage Schema
How do I find the right development workflow skill for a specific coding task?

Skill discovery maps task intent to named engineering workflows, matching development phases like idea refinement, spec-driven development, or code review to the appropriate operational rules and verification steps.

When should I use spec-driven development versus incremental implementation?

Spec-driven development fits when defining requirements upfront, while incremental-implementation applies when building a feature in smaller slices; the meta-skill routes your task intent to the matching workflow.

What's the best way to ensure verification steps are applied during code reviews?

Code review and quality enforcement loads the selected skill's operating behaviors and verification checklist, surfacing assumptions and managing confusion before marking work done.

Does this meta-skill work with test-driven development workflows?

Yes, it routes testing phase tasks to the test-driven-development skill, loading its specific operating behaviors, failure-mode checks, and verification rules before execution begins.

What happens if the wrong engineering workflow is applied to a feature request?

Misapplied processes cause missed verification steps, but the meta-skill prevents this by matching task intent to the correct skill, enforcing governance and safety checks before completion.