القائمة
Index of all available skills across both GitHub Copilot (.github/skills/) and Gemini CLI (.gemini/skills/). Load this to find the right skill for a task, or to locate the counterpart skill in the other AI system.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skills-overview |
| description | Index of all available skills across both GitHub Copilot (.github/skills/) and Gemini CLI (.gemini/skills/). Load this to find the right skill for a task, or to locate the counterpart skill in the other AI system. |
Two AI assistants are configured for this project, each with their own skill directory:
.github/skills/.gemini/skills/Skills with the same purpose exist in both, sometimes under different names and with different depth. This index maps them so you can find the richer version when needed.
| Topic | Copilot Skill | Gemini Skill | Notes |
|---|---|---|---|
| Testing | testing-workflow | testing-workflow | Copilot version covers testFailure tool and PYTHONPATH; Gemini version emphasises full suite preference and container detection |
| Settings & config | settings-management | settings | Gemini version is more comprehensive (22-point guide + PR checklist); Copilot version covers ccd() and get_setting_value() usage |
| MCP activation | mcp-activation | mcp-activation | Copilot version covers VS Code window reload; Gemini version covers Gemini CLI session restart |
| Project navigation | project-navigation | project-navigation | Copilot version has full path tables and env vars; Gemini version is a brief reference |
| Plugin dev | plugin-run-development | plugin-development | Copilot version is comprehensive (data contract, phases, formats); Gemini version is a brief checklist pointing to docs/PLUGINS_DEV.md |
| Devcontainer | devcontainer-services + devcontainer-setup + devcontainer-configs | devcontainer-management | Copilot splits into 3 focused skills; Gemini combines into one (uses docker exec) |
No Gemini equivalent yet:
| Skill | Purpose |
|---|---|
api-development | Creating REST API endpoints |
authentication | API tokens and 401/403 debugging |
code-standards | Coding conventions and style rules |
database-patterns | Device table write paths, SQLite triggers, audit logging, *Source attribution |
database-reset | Wipe and regenerate the database and config |
docker-build | Build Docker images for testing or production |
docker-prune | Clean unused Docker resources (destructive — requires confirmation) |
sample-data | Load synthetic device data into the devcontainer |
No Copilot equivalent yet:
| Skill | Purpose |
|---|---|
initiative-start | Research methodology and structured approach for new tasks |
When adding a skill, create it in both directories to keep both AI systems current:
.github/skills/<name>/SKILL.md — add an entry to the skills table in .github/copilot-instructions.md.gemini/skills/<name>/SKILL.md — auto-discovered by Gemini CLI via YAML frontmatterKeep the body content identical between both files. Only the frontmatter name/description may differ slightly to match each system's discovery heuristics.
Enables live interaction with the NetAlertX runtime. This skill configures the Model Context Protocol (MCP) connection, granting full API access for debugging, troubleshooting, and real-time operations including database queries, network scans, and device management.
Reference for the NetAlertX codebase structure, key file paths, and configuration locations. Use this when exploring the codebase or looking for specific components like the backend entry point, frontend files, or database location.
Best practices for creating and maintaining NetAlertX settings (config.json), including UI, validation, localization, runtime behavior, and implementation consistency.
Index of all available skills across both Gemini CLI (.gemini/skills/) and GitHub Copilot (.github/skills/). Load this to find the right skill for a task, or to locate the counterpart skill in the other AI system.
Read before running tests. Detailed instructions for single, standard unit tests (fast), full suites (slow), handling authentication, and obtaining the API Token. Tests must be run when a job is complete.
NetAlertX database architecture patterns. Use this when designing features that write to the Devices table, implementing audit/history logging, or choosing between trigger-based vs Python-hook approaches.