[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77XTTHBXZDNBWR9PRARMH5B":3,"skill-same:01M77XTTHBXZDNBWR9PRARMH5B":92},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":45,"install":46,"resources":58},"01M77XTTHBXZDNBWR9PRARMH5B","skill-creator-flagos",null,"Create new skills, modify existing skills, and validate skill quality for the FlagOS skills repository. Use this skill whenever someone wants to create a skill from scratch, improve or edit an existing skill, scaffold a new skill directory, validate skill structure, or run test cases against a skill. Trigger when the user says things like \"create a skill\", \"make a new skill for X\", \"scaffold a skill\", \"improve this skill\", \"validate my skill\", or simply \"\u002Fskill-creator-flagos\". Also trigger when users mention turning a workflow into a reusable skill, or want to package a repeated process as a skill.","Jinhong270\u002FAI-Agent","Jinhong270","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193703602?v=4","01M77SB4J7ATDYATSD7AW4B8XP","01M77SB4JWRQWNGTTR291BHMQP",3,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-creator-flagos\ndescription: >\n  Create new skills, modify existing skills, and validate skill quality for the FlagOS skills\n  repository. Use this skill whenever someone wants to create a skill from scratch, improve or\n  edit an existing skill, scaffold a new skill directory, validate skill structure, or run test\n  cases against a skill. Trigger when the user says things like \"create a skill\", \"make a new\n  skill for X\", \"scaffold a skill\", \"improve this skill\", \"validate my skill\", or simply\n  \"\u002Fskill-creator-flagos\". Also trigger when users mention turning a workflow into a reusable skill,\n  or want to package a repeated process as a skill.\nargument-hint: \"[skill-name] [--init | --validate | --eval]\"\nuser-invokable: true\ncompatibility: \"Python 3.8+, works with any AI coding assistant that supports the Agent Skills standard\"\nmetadata:\n  version: \"1.0.0\"\n  author: flagos-ai\n  category: workflow-automation\n  tags: [skill-creation, scaffolding, validation, meta-skill, developer-tooling]\nallowed-tools: \"Bash(python3:*) Bash(python:*) Bash(chmod:*) Bash(mkdir:*) Bash(cp:*) Bash(ls:*) Bash(cat:*) Read Edit Write Glob Grep AskUserQuestion TaskCreate TaskUpdate TaskList TaskGet Agent\"\n---\n\n# Skill Creator\n\nA meta-skill for creating, improving, and validating skills in the FlagOS skills repository.\n\n## Overview\n\nThis skill guides you through the full lifecycle of skill development:\n1. **Create** — scaffold a new skill from template, interview the user, write SKILL.md\n2. **Improve** — analyze an existing skill, identify weaknesses, iterate with test cases\n3. **Validate** — check structure, frontmatter, references, and conventions compliance\n\n## Usage\n\n```\n\u002Fskill-creator-flagos                       # Interactive — asks what you want to do\n\u002Fskill-creator-flagosmy-new-skill --init    # Scaffold a new skill\n\u002Fskill-creator-flagosmy-skill --validate    # Validate an existing skill\n\u002Fskill-creator-flagosmy-skill --eval        # Run test prompts against a skill\n```\n\n## Execution\n\n### Step 0: Parse arguments and determine mode\n\nExtract from user input:\n- `{{skill_name}}` — optional skill name (hyphen-case)\n- `{{mode}}` — one of: `create`, `improve`, `validate`, `eval`, or `interactive` (default)\n\nIf no mode is specified, ask the user:\n\n> What would you like to do?\n> 1. Create a new skill from scratch\n> 2. Improve an existing skill\n> 3. Validate a skill's structure and conventions\n> 4. Run test cases against a skill\n\n**-> Tell user**: Confirm the mode and skill name.\n\n---\n\n## Mode 1: Create a New Skill\n\n### Step 1: Capture intent\n\nStart by understanding what the user wants to build. If the current conversation already contains a workflow the user wants to capture (e.g., \"turn this into a skill\"), extract answers from the conversation history first.\n\nKey questions to clarify:\n1. What should this skill enable the agent to do?\n2. When should this skill trigger? (user phrases, contexts, file types)\n3. What's the expected output or end state?\n4. Does the skill need scripts, reference docs, or asset files?\n5. What tools does the skill need access to?\n\nAdapt your communication style to the user — don't assume coding jargon familiarity. Pay attention to context cues.\n\n**-> Tell user**: Summarize the captured intent and confirm before proceeding.\n\n### Step 2: Initialize the skill directory\n\nRun the init script to scaffold the skill:\n\n```bash\npython3 {{skill_root}}\u002Fscripts\u002Finit_skill.py {{skill_name}} --path {{skills_dir}} [--resources scripts,references,assets]\n```\n\nWhere:\n- `{{skill_root}}` = absolute path to this skill-creator-flagos's directory\n- `{{skills_dir}}` = path to the `skills\u002F` directory (usually the parent of `{{skill_root}}`)\n\nThe script creates the directory with SKILL.md template, LICENSE.txt, and optional subdirectories.\n\n**-> Tell user**: Show the created directory structure.\n\n### Step 3: Write the SKILL.md\n\nBased on the user interview, fill in these components:\n\n#### Frontmatter (YAML)\n\n| Field | Required | Guidelines |\n|-------|----------|------------|\n| `name` | Yes | Lowercase + hyphens, must match directory name, max 64 chars |\n| `description` | Yes | 1-2 sentences: what it does AND when to trigger. Be specific and slightly \"pushy\" — err on the side of triggering too often rather than too rarely |\n| `argument-hint` | Recommended | Show expected arguments |\n| `user-invokable` | Recommended | `true` if invokable via `\u002Fskill-name` |\n| `compatibility` | Optional | Environment requirements |\n| `metadata` | Recommended | version, author, category, tags |\n| `allowed-tools` | Recommended | Space-separated tool list with patterns |\n\n#### Body (Markdown)\n\nFollow the structure documented in `references\u002Fwriting-guide.md`. At minimum include:\n- **Overview** — what problem this solves, when to activate\n- **Prerequisites** — environment requirements\n- **Execution steps** — numbered steps with `**-> Tell user**` progress markers\n- **Examples** — at least 2-3 realistic usage examples\n- **Troubleshooting** — common problems and fixes\n\nRead `references\u002Fwriting-guide.md` for detailed patterns on progressive disclosure, output formats, domain organization, and writing style.\n\n### Step 4: Add supporting resources\n\nBased on the skill's needs, create:\n- **`scripts\u002F`** — executable code for deterministic\u002Frepetitive tasks\n- **`references\u002F`** — detailed docs loaded into context as needed\n- **`assets\u002F`** — files used in output (templates, icons, etc.)\n\nRules:\n- Every script\u002Freference must be documented in SKILL.md with usage instructions\n- Scripts should have execute permissions (`chmod +x`)\n- Keep SKILL.md under 500 lines; move detailed content to `references\u002F`\n- For reference files >300 lines, include a table of contents\n\n### Step 5: Validate\n\nRun validation to check conventions compliance:\n\n```bash\npython3 {{repo_root}}\u002Fscripts\u002Fvalidate_skills.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nFix any reported issues. See Troubleshooting section below.\n\n**-> Tell user**: Report validation results. On failure, diagnose and fix.\n\n### Step 6: Write README files\n\nCreate `README.md` (English) and optionally `README_zh.md` (Chinese) following the pattern in existing skills. The README should cover:\n- Overview \u002F problem statement\n- Usage instructions\n- Directory structure\n- File descriptions\n- Examples\n- Installation instructions\n\n**-> Tell user**: Skill creation complete. Present the final directory tree and summary.\n\n---\n\n## Mode 2: Improve an Existing Skill\n\n### Step 1: Analyze the current skill\n\nRead the existing SKILL.md and all supporting files. Identify:\n- Unclear or missing trigger conditions in the description\n- Missing examples or edge cases\n- Steps that lack progress reporting (`**-> Tell user**`)\n- Overly long SKILL.md that should be split into references\n- Missing troubleshooting entries\n- Scripts without documentation\n\n**-> Tell user**: Present findings and proposed improvements.\n\n### Step 2: Draft test prompts\n\nCreate 2-3 realistic test prompts — things a real user would say. Share them with the user for confirmation.\n\nSave to `evals\u002Fevals.json`:\n\n```json\n{\n  \"skill_name\": \"{{skill_name}}\",\n  \"evals\": [\n    {\n      \"id\": 1,\n      \"prompt\": \"User's task prompt\",\n      \"expected_output\": \"Description of expected result\",\n      \"assertions\": [\"The output includes X\", \"Step Y was executed\"]\n    }\n  ]\n}\n```\n\nSee `references\u002Fschemas.md` for the full schema.\n\n### Step 3: Iterate\n\nFor each round:\n1. Apply improvements to SKILL.md and supporting files\n2. Re-run validation\n3. Review against test prompts (mentally or by spawning test runs)\n4. Collect user feedback\n5. Repeat until satisfied\n\n**-> Tell user**: Report changes made in each iteration.\n\n---\n\n## Mode 3: Validate\n\nRun the validation script:\n\n```bash\npython3 {{repo_root}}\u002Fscripts\u002Fvalidate_skills.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nThe script checks:\n- SKILL.md exists and has valid YAML frontmatter\n- Required fields (`name`, `description`) are present\n- `name` matches directory name, follows naming conventions\n- `description` length within limits\n- Body has sufficient content (>100 chars)\n- Referenced files in `scripts\u002F` and `references\u002F` actually exist\n- Scripts have execute permissions\n- No hardcoded paths or credentials\n\n**-> Tell user**: Report all findings with severity (error\u002Fwarning).\n\n---\n\n## Mode 4: Run Evals\n\nIf `evals\u002Fevals.json` exists, run the test prompts against the skill:\n\n```bash\npython3 {{skill_root}}\u002Fscripts\u002Frun_eval.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nThis generates a report showing which assertions passed\u002Ffailed for each test case.\n\n**-> Tell user**: Present results and suggest improvements.\n\n---\n\n## Placeholders\n\n| Placeholder | How to derive |\n|---|---|\n| `{{skill_name}}` | From user input, normalized to hyphen-case |\n| `{{skill_root}}` | Absolute path to this skill-creator-flagos's directory |\n| `{{repo_root}}` | Absolute path to the repository root (parent of `skills\u002F`) |\n| `{{skills_dir}}` | Path to the `skills\u002F` directory containing all skills |\n\n## Examples\n\n**Example 1: Create a new skill from scratch**\n```\nUser says: \"\u002Fskill-creator-flagospreflight-check --init\"\nActions:\n  1. Parse → skill_name=preflight-check, mode=create\n  2. Interview user about what preflight-check should do\n  3. Run init_skill.py to scaffold directory\n  4. Write SKILL.md with deployment verification workflow\n  5. Add scripts\u002Fcheck_gpu.sh, scripts\u002Fcheck_env.py\n  6. Validate and fix any issues\n  7. Write README.md\nResult: Complete preflight-check skill ready for use\n```\n\n**Example 2: Improve an existing skill**\n```\nUser says: \"improve model-migrate-flagos, the description could be better\"\nActions:\n  1. Read existing SKILL.md and all references\n  2. Analyze description — find it's too long and not trigger-friendly\n  3. Propose a more concise, trigger-optimized description\n  4. Create test prompts to verify triggering\n  5. Apply changes, validate\nResult: Improved skill with better triggering accuracy\n```\n\n**Example 3: Validate all skills**\n```\nUser says: \"\u002Fskill-creator-flagos--validate\"\nActions:\n  1. No skill_name provided → validate all skills in skills\u002F\n  2. Run validate_skill.py on each skill directory\n  3. Report consolidated results\nResult: Validation report for all skills\n```\n\n**Example 4: Turn a conversation workflow into a skill**\n```\nUser says: \"turn what we just did into a skill\"\nActions:\n  1. Analyze conversation history for the workflow performed\n  2. Extract: tools used, sequence of steps, corrections made\n  3. Interview user to fill gaps\n  4. Scaffold and write the skill\nResult: New skill capturing the conversation workflow\n```\n\n## Troubleshooting\n\n| Problem | Cause | Fix |\n|---|---|---|\n| `name does not match directory name` | Frontmatter `name` differs from folder name | Ensure they are identical |\n| `description exceeds 1024 chars` | Description too long | Move details to the body; keep description to 1-2 sentences |\n| `SKILL.md body is too short` | Insufficient instructions | Add overview, steps, examples, troubleshooting |\n| `Missing required field` | `name` or `description` absent in frontmatter | Add the missing field |\n| `name must be lowercase+hyphens` | Invalid characters in name | Use only `a-z`, `0-9`, `-` |\n| Skill doesn't trigger | Description too narrow or vague | Make description more specific and slightly aggressive about triggering |\n| Referenced file not found | Script or reference listed in SKILL.md but not on disk | Create the file or remove the reference |\n","# Skill Creator\n\nA meta-skill for creating, improving, and validating skills in the FlagOS skills repository.\n\n## Overview\n\nThis skill guides you through the full lifecycle of skill development:\n1. **Create** — scaffold a new skill from template, interview the user, write SKILL.md\n2. **Improve** — analyze an existing skill, identify weaknesses, iterate with test cases\n3. **Validate** — check structure, frontmatter, references, and conventions compliance\n\n## Usage\n\n```\n\u002Fskill-creator-flagos                       # Interactive — asks what you want to do\n\u002Fskill-creator-flagosmy-new-skill --init    # Scaffold a new skill\n\u002Fskill-creator-flagosmy-skill --validate    # Validate an existing skill\n\u002Fskill-creator-flagosmy-skill --eval        # Run test prompts against a skill\n```\n\n## Execution\n\n### Step 0: Parse arguments and determine mode\n\nExtract from user input:\n- `{{skill_name}}` — optional skill name (hyphen-case)\n- `{{mode}}` — one of: `create`, `improve`, `validate`, `eval`, or `interactive` (default)\n\nIf no mode is specified, ask the user:\n\n> What would you like to do?\n> 1. Create a new skill from scratch\n> 2. Improve an existing skill\n> 3. Validate a skill's structure and conventions\n> 4. Run test cases against a skill\n\n**-> Tell user**: Confirm the mode and skill name.\n\n---\n\n## Mode 1: Create a New Skill\n\n### Step 1: Capture intent\n\nStart by understanding what the user wants to build. If the current conversation already contains a workflow the user wants to capture (e.g., \"turn this into a skill\"), extract answers from the conversation history first.\n\nKey questions to clarify:\n1. What should this skill enable the agent to do?\n2. When should this skill trigger? (user phrases, contexts, file types)\n3. What's the expected output or end state?\n4. Does the skill need scripts, reference docs, or asset files?\n5. What tools does the skill need access to?\n\nAdapt your communication style to the user — don't assume coding jargon familiarity. Pay attention to context cues.\n\n**-> Tell user**: Summarize the captured intent and confirm before proceeding.\n\n### Step 2: Initialize the skill directory\n\nRun the init script to scaffold the skill:\n\n```bash\npython3 {{skill_root}}\u002Fscripts\u002Finit_skill.py {{skill_name}} --path {{skills_dir}} [--resources scripts,references,assets]\n```\n\nWhere:\n- `{{skill_root}}` = absolute path to this skill-creator-flagos's directory\n- `{{skills_dir}}` = path to the `skills\u002F` directory (usually the parent of `{{skill_root}}`)\n\nThe script creates the directory with SKILL.md template, LICENSE.txt, and optional subdirectories.\n\n**-> Tell user**: Show the created directory structure.\n\n### Step 3: Write the SKILL.md\n\nBased on the user interview, fill in these components:\n\n#### Frontmatter (YAML)\n\n| Field | Required | Guidelines |\n|-------|----------|------------|\n| `name` | Yes | Lowercase + hyphens, must match directory name, max 64 chars |\n| `description` | Yes | 1-2 sentences: what it does AND when to trigger. Be specific and slightly \"pushy\" — err on the side of triggering too often rather than too rarely |\n| `argument-hint` | Recommended | Show expected arguments |\n| `user-invokable` | Recommended | `true` if invokable via `\u002Fskill-name` |\n| `compatibility` | Optional | Environment requirements |\n| `metadata` | Recommended | version, author, category, tags |\n| `allowed-tools` | Recommended | Space-separated tool list with patterns |\n\n#### Body (Markdown)\n\nFollow the structure documented in `references\u002Fwriting-guide.md`. At minimum include:\n- **Overview** — what problem this solves, when to activate\n- **Prerequisites** — environment requirements\n- **Execution steps** — numbered steps with `**-> Tell user**` progress markers\n- **Examples** — at least 2-3 realistic usage examples\n- **Troubleshooting** — common problems and fixes\n\nRead `references\u002Fwriting-guide.md` for detailed patterns on progressive disclosure, output formats, domain organization, and writing style.\n\n### Step 4: Add supporting resources\n\nBased on the skill's needs, create:\n- **`scripts\u002F`** — executable code for deterministic\u002Frepetitive tasks\n- **`references\u002F`** — detailed docs loaded into context as needed\n- **`assets\u002F`** — files used in output (templates, icons, etc.)\n\nRules:\n- Every script\u002Freference must be documented in SKILL.md with usage instructions\n- Scripts should have execute permissions (`chmod +x`)\n- Keep SKILL.md under 500 lines; move detailed content to `references\u002F`\n- For reference files >300 lines, include a table of contents\n\n### Step 5: Validate\n\nRun validation to check conventions compliance:\n\n```bash\npython3 {{repo_root}}\u002Fscripts\u002Fvalidate_skills.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nFix any reported issues. See Troubleshooting section below.\n\n**-> Tell user**: Report validation results. On failure, diagnose and fix.\n\n### Step 6: Write README files\n\nCreate `README.md` (English) and optionally `README_zh.md` (Chinese) following the pattern in existing skills. The README should cover:\n- Overview \u002F problem statement\n- Usage instructions\n- Directory structure\n- File descriptions\n- Examples\n- Installation instructions\n\n**-> Tell user**: Skill creation complete. Present the final directory tree and summary.\n\n---\n\n## Mode 2: Improve an Existing Skill\n\n### Step 1: Analyze the current skill\n\nRead the existing SKILL.md and all supporting files. Identify:\n- Unclear or missing trigger conditions in the description\n- Missing examples or edge cases\n- Steps that lack progress reporting (`**-> Tell user**`)\n- Overly long SKILL.md that should be split into references\n- Missing troubleshooting entries\n- Scripts without documentation\n\n**-> Tell user**: Present findings and proposed improvements.\n\n### Step 2: Draft test prompts\n\nCreate 2-3 realistic test prompts — things a real user would say. Share them with the user for confirmation.\n\nSave to `evals\u002Fevals.json`:\n\n```json\n{\n  \"skill_name\": \"{{skill_name}}\",\n  \"evals\": [\n    {\n      \"id\": 1,\n      \"prompt\": \"User's task prompt\",\n      \"expected_output\": \"Description of expected result\",\n      \"assertions\": [\"The output includes X\", \"Step Y was executed\"]\n    }\n  ]\n}\n```\n\nSee `references\u002Fschemas.md` for the full schema.\n\n### Step 3: Iterate\n\nFor each round:\n1. Apply improvements to SKILL.md and supporting files\n2. Re-run validation\n3. Review against test prompts (mentally or by spawning test runs)\n4. Collect user feedback\n5. Repeat until satisfied\n\n**-> Tell user**: Report changes made in each iteration.\n\n---\n\n## Mode 3: Validate\n\nRun the validation script:\n\n```bash\npython3 {{repo_root}}\u002Fscripts\u002Fvalidate_skills.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nThe script checks:\n- SKILL.md exists and has valid YAML frontmatter\n- Required fields (`name`, `description`) are present\n- `name` matches directory name, follows naming conventions\n- `description` length within limits\n- Body has sufficient content (>100 chars)\n- Referenced files in `scripts\u002F` and `references\u002F` actually exist\n- Scripts have execute permissions\n- No hardcoded paths or credentials\n\n**-> Tell user**: Report all findings with severity (error\u002Fwarning).\n\n---\n\n## Mode 4: Run Evals\n\nIf `evals\u002Fevals.json` exists, run the test prompts against the skill:\n\n```bash\npython3 {{skill_root}}\u002Fscripts\u002Frun_eval.py {{skills_dir}}\u002F{{skill_name}}\n```\n\nThis generates a report showing which assertions passed\u002Ffailed for each test case.\n\n**-> Tell user**: Present results and suggest improvements.\n\n---\n\n## Placeholders\n\n| Placeholder | How to derive |\n|---|---|\n| `{{skill_name}}` | From user input, normalized to hyphen-case |\n| `{{skill_root}}` | Absolute path to this skill-creator-flagos's directory |\n| `{{repo_root}}` | Absolute path to the repository root (parent of `skills\u002F`) |\n| `{{skills_dir}}` | Path to the `skills\u002F` directory containing all skills |\n\n## Examples\n\n**Example 1: Create a new skill from scratch**\n```\nUser says: \"\u002Fskill-creator-flagospreflight-check --init\"\nActions:\n  1. Parse → skill_name=preflight-check, mode=create\n  2. Interview user about what preflight-check should do\n  3. Run init_skill.py to scaffold directory\n  4. Write SKILL.md with deployment verification workflow\n  5. Add scripts\u002Fcheck_gpu.sh, scripts\u002Fcheck_env.py\n  6. Validate and fix any issues\n  7. Write README.md\nResult: Complete preflight-check skill ready for use\n```\n\n**Example 2: Improve an existing skill**\n```\nUser says: \"improve model-migrate-flagos, the description could be better\"\nActions:\n  1. Read existing SKILL.md and all references\n  2. Analyze description — find it's too long and not trigger-friendly\n  3. Propose a more concise, trigger-optimized description\n  4. Create test prompts to verify triggering\n  5. Apply changes, validate\nResult: Improved skill with better triggering accuracy\n```\n\n**Example 3: Validate all skills**\n```\nUser says: \"\u002Fskill-creator-flagos--validate\"\nActions:\n  1. No skill_name provided → validate all skills in skills\u002F\n  2. Run validate_skill.py on each skill directory\n  3. Report consolidated results\nResult: Validation report for all skills\n```\n\n**Example 4: Turn a conversation workflow into a skill**\n```\nUser says: \"turn what we just did into a skill\"\nActions:\n  1. Analyze conversation history for the workflow performed\n  2. Extract: tools used, sequence of steps, corrections made\n  3. Interview user to fill gaps\n  4. Scaffold and write the skill\nResult: New skill capturing the conversation workflow\n```\n\n## Troubleshooting\n\n| Problem | Cause | Fix |\n|---|---|---|\n| `name does not match directory name` | Frontmatter `name` differs from folder name | Ensure they are identical |\n| `description exceeds 1024 chars` | Description too long | Move details to the body; keep description to 1-2 sentences |\n| `SKILL.md body is too short` | Insufficient instructions | Add overview, steps, examples, troubleshooting |\n| `Missing required field` | `name` or `description` absent in frontmatter | Add the missing field |\n| `name must be lowercase+hyphens` | Invalid characters in name | Use only `a-z`, `0-9`, `-` |\n| Skill doesn't trigger | Description too narrow or vague | Make description more specific and slightly aggressive about triggering |\n| Referenced file not found | Script or reference listed in SKILL.md but not on disk | Create the file or remove the reference |\n",{"name":5,"metadata":24,"description":34,"allowed-tools":35,"argument-hint":36,"compatibility":37,"user-invokable":38},{"tags":25,"author":31,"version":32,"category":33},[26,27,28,29,30],"skill-creation","scaffolding","validation","meta-skill","developer-tooling","flagos-ai","1.0.0","workflow-automation","Create new skills, modify existing skills, and validate skill quality for the FlagOS skills repository. Use this skill whenever someone wants to create a skill from scratch, improve or edit an existing skill, scaffold a new skill directory, validate skill structure, or run test cases against a skill. Trigger when the user says things like \"create a skill\", \"make a new skill for X\", \"scaffold a skill\", \"improve this skill\", \"validate my skill\", or simply \"\u002Fskill-creator-flagos\". Also trigger when users mention turning a workflow into a reusable skill, or want to package a repeated process as a skill.\n","Bash(python3:*) Bash(python:*) Bash(chmod:*) Bash(mkdir:*) Bash(cp:*) Bash(ls:*) Bash(cat:*) Read Edit Write Glob Grep AskUserQuestion TaskCreate TaskUpdate TaskList TaskGet Agent","[skill-name] [--init | --validate | --eval]","Python 3.8+, works with any AI coding assistant that supports the Agent Skills standard",true,"main","cb3f39689b7b3a95edb2753c8f3e97a313b885fc","Xiao-Q\u002Fskills\u002Fskill-creator-flagos-cn",0,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent","https:\u002F\u002Fgithub.com\u002FJinhong270","2026-09-30 23:42:56",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":38},[48,51,54],{"tool":49,"command":50},"npx","npx skills add Jinhong270\u002FAI-Agent --skill skill-creator-flagos",{"tool":52,"command":53},"bunx","bunx skills add Jinhong270\u002FAI-Agent --skill skill-creator-flagos",{"tool":55,"command":56},"pnpm","pnpm dlx skills add Jinhong270\u002FAI-Agent --skill skill-creator-flagos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002FSKILL.md",[59,65,70,74,78,82,86],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"_meta.json","REFERENCE","参考文档",116,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002F_meta.json",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",11262,{"path":71,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":72,"sourceHtmlUrl":73},"README_zh.md",11050,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002FREADME_zh.md",{"path":75,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":76,"sourceHtmlUrl":77},"README.md",11951,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002FREADME.md",{"path":79,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fschemas.md",3102,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002Freferences\u002Fschemas.md",{"path":83,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fwriting-guide.md",9745,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002Freferences\u002Fwriting-guide.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"scripts\u002Finit_skill.py","SCRIPT","脚本",6476,"https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fskill-creator-flagos-cn\u002Fscripts\u002Finit_skill.py",[93,101,109,116,123,130],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M77Z0W1XHJVFS4M183VZTF3Z","xlsx","Open, create, read, analyze, edit, repair, or validate spreadsheet files (.xlsx, .xlsm, .xltx, .csv, .tsv) with zero format loss, with first-class support for Chinese \u002F CJK content. Use whenever the user asks to create, build, modify, fill, analyze, read, repair, validate, or format any spreadsheet, workbook, report, dashboard, budget, financial model, pivot table, or tabular data file. Handles Chinese text, encodings (UTF-8 \u002F GB18030 \u002F GBK), full-width characters, CJK fonts in rendering, and Chinese number\u002Fdate conventions (¥, 万\u002F亿, 年\u002F月\u002F日). Covers: creating new workbooks from scratch, reading and analyzing existing files, editing existing workbooks while preserving pivot tables \u002F VBA macros \u002F charts \u002F sparklines \u002F conditional formatting \u002F named ranges, formula recalculation and validation, visual review of results, and applying professional formatting. Triggers on 'spreadsheet', 'Excel', 'workbook', '表格', '工作簿', '.xlsx', '.xlsm', '.csv', 'pivot table', '透视表', 'macro', '宏', 'chart', '图表', 'financial model', '财务模型', 'formula', '公式', or any request to produce tabular data.","MIT","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxlsx007-skill\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M77Z0EVYYQEYGJME2K56STBZ","xlsx-formula-master","你描述需求(人话)，它给你 Excel \u002F WPS 公式 + 解释 + 不踩坑的边界条件。\n专攻 VLOOKUP \u002F XLOOKUP \u002F INDEX-MATCH \u002F SUMIFS \u002F 数组公式 \u002F 动态数组 \u002F Power Query 等高频但易错场景。\n自动适配你的 Excel 版本（2019 \u002F 365 \u002F WPS）——版本不同公式可能不能用。\n触发：用户说 \"Excel 公式\"、\"VLOOKUP\"、\"怎么算\"、\"WPS 公式\"、\"求和怎么写\"、\"匹配数据\"、\"数据透视\"。","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxlsx-formula-master\u002FLICENSE.md","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxlsx-formula-master\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M77Z05X53XF8VVQFFFZE2Z4Z","self-improving-agent","Self-improving agent system that analyzes conversation quality, identifies improvement opportunities, and continuously optimizes response strategies.","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxiucheng-self-improving-agent\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M77YZ7KXV2B7GDCBKE07QRWE","xiaohongshu-content-tools","小红书运营数据工具｜当提到小红书关键词搜索,小红书笔记详情及评论,小红书博主作品时使用，可实现爆款挖掘\u002F竞品分析\u002FKOL筛选\u002F趋势洞察，用数据驱动小红书流量增长，告别盲目创作","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxiaohongshu-content-tools\u002FSKILL.md",[],[],{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":19},"01M77YYQVPA4EWZPQ8J88BYVYA","xfg-ddd-skills","DDD 六边形架构设计与部署技能包。提供 Domain\u002FCase\u002FInfrastructure 层设计模式与代码模板，以及 Docker 环境部署脚本。当用户询问 DDD 架构、设计模式或需要部署项目时调用。","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fxfg-ddd-skills\u002FSKILL.md",[],[],{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":19},"01M77YXP7QKKD0HX26W2V63Q9M","wordpress","WordPress.com API integration with managed OAuth. Manage posts, pages, sites, and content.\nUse this skill when users want to create, read, update, or delete WordPress.com posts, pages, or manage site content.\nFor other third party apps, use the api-gateway skill (https:\u002F\u002Fclawhub.ai\u002Fbyungkyu\u002Fapi-gateway).\nRequires network access and valid Maton API key.","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fwordpress-api\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FJinhong270\u002FAI-Agent\u002Fblob\u002Fmain\u002FXiao-Q\u002Fskills\u002Fwordpress-api\u002FSKILL.md",[],[]]