skill scout

Engineering Community

Skill notes

When to Use

The user says "create a skill", "build a skill", "make a skill", or "new skill". The user asks "is there a skill for X?" or "does a skill exist that does Y?" The user describes a workflow and you are about to suggest creating a new skill.

Step 1 - Capture Intent

Extract: The task the skill should perform. The trigger conditions for using it. The domain, tools, frameworks, or data sources involved. Three to five search keywords plus useful synonyms.

Step 2 - Search Local Sources

Search installed and marketplace skill names first. Local sources are preferred because they are already part of the user's environment. Then search frontmatter descriptions:

Step 3 - Search Remote Sources

Use available GitHub and web search tools. Prefer concise queries: For web search, use at most three targeted queries such as:

Step 4 - Vet External Matches

Before recommending any external skill for adoption or forking: Read the SKILL.md frontmatter and instructions. Look for unexpected shell commands, file writes, network calls, credential handling, or package installs. Check whether the repository appears maintained.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@affaan-m · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-scout.preview
# Step 5 - Rank Results

1. Exact keyword match in the skill name.
2. Keyword or synonym match in description.
3. Local installed or marketplace source.
4. Maintained GitHub source with recent activity.
5. Web-only mention.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.