skill from github

Engineering Community

Skill notes

When to Use

When users describe a task and you want to find existing tools/projects to learn from: "I want to be able to convert markdown to PDF" "Help me analyze sentiment in customer reviews" "I need to generate API documentation from code"

Step 1: Understand User Intent

Clarify what the user wants to achieve: What is the input? What is the expected output? Any constraints (language, framework, etc.)?

Step 2: Search GitHub

Search for projects that solve this problem: Search tips: Start broad, then narrow down Try different keyword combinations Include "cli", "tool", "library" if relevant

Step 3: Present Options to User

Show top 3-5 candidates: Wait for user confirmation before proceeding.

Step 4: Deep Dive into Selected Project

Once user selects a project, thoroughly understand it: Read README - Understand purpose, features, usage Read core source files - Understand how it works Check examples - See real usage patterns Note dependencies - What it relies on

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
@GBSOSS · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
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
Network behavior
Local-only
Install commands
None (reference only)

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

01
Step 1: Understand User Intent

Clarify what the user wants to achieve: What is the input? What is the expected output? Any constraints (language, framework, etc.)?

02
Step 2: Search GitHub

Search for projects that solve this problem: Search tips: Start broad, then narrow down Try different keyword combinations Include "cli", "tool", "library" if relevant

03
Step 3: Present Options to User

Show top 3-5 candidates: Wait for user confirmation before proceeding.

04
Step 4: Deep Dive into Selected Project

Once user selects a project, thoroughly understand it: Read README - Understand purpose, features, usage Read core source files - Understand how it works Check examples - See real usage patterns Note dependencies - What it relies on

05
Step 5: Summarize Understanding

Present what you learned to user: Wait for user confirmation.

06
Step 6: Create Skill via skill-creator

Hand off to skill-creator with: Clear purpose - What the skill does Methodology - The approach learned from the project Step-by-step process - Concrete instructions Quality criteria - What good output looks like

Discussion

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