القائمة
Use this skill when the user wants to create a new skill or remove an existing skill. This includes writing a SKILL.md from scratch and adding scripts/assets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use this skill when the user wants a memory feed — a scheduled automation that fetches targeted data from their integrations (gmail/calendar/slack/web) and keeps ONE memory page current, updated in place. Examples; "track my PR queue", "keep an invoices page", "week-ahead brief".
Implement a spec end-to-end — recon readers map the codebase, an architect pins every cross-file contract in a blueprint, parallel builders implement disjoint workstreams from it, adversarial review, then a final test gate. Use for multi-file feature work. Run via the workflow tool by name.
Find -> adversarially verify -> rank issues over a target (a diff, dir, file, or glob). Use for code review, a scoped bug hunt, a security or perf pass. Run via the workflow tool by name.
Answer a question about a target by fanning out parallel readers over derived angles, then synthesizing a cited answer. Use to understand a subsystem, research a question, or trace how/where something works. Run via the workflow tool by name.
Decide between approaches — generate N diverse proposals from different lenses, score each against criteria with independent judges, then synthesize a decisive recommendation. Use for design choices, tradeoff calls, "which approach should we take". Run via the workflow tool by name.
Use this skill when the user wants to turn the current conversation into a scheduled automation. Analyze the session and call create_automation to propose one — the user reviews the full prompt + schedule in the approval card before it's saved.
استنادا إلى تصنيف SOC المهني
| name | add-skill |
| description | Use this skill when the user wants to create a new skill or remove an existing skill. This includes writing a SKILL.md from scratch and adding scripts/assets. |
Skills are discovered from three places:
.skills/ under the server working directory~/.ntrp/skills/ — user skills, create hereA skill is a directory containing at minimum a SKILL.md file.
~/.ntrp/skills/my-skill/
├── SKILL.md # required
├── scripts/ # optional: executable scripts
├── references/ # optional: extra docs loaded on demand
└── assets/ # optional: templates, data files
---
name: my-skill
description: What it does and WHEN to use it. Be specific — this is what I read to decide whether to activate the skill.
---
# Skill Title
Step-by-step instructions...
name: lowercase, hyphens only, must match directory name, max 64 charsdescription: max 1024 chars — include keywords that match user intent~/.ntrp/skills/<name>/) or project-local (.skills/<name>/). Default to global unless the user asks for project-local behavior.mkdir -p <target>/<name>/scriptsSKILL.md with frontmatter + instructions<skill_path>/... in SKILL.mdDelete the directory. Only project/global skills can be removed (not builtins).
ls ~/.ntrp/skills/
ls /Users/escept1co/src/ntrp/skills/
<available_skills>use_skill(skill="<name>")SKILL.md under 500 lines — move heavy reference material to references/<skill_path> at load time — use it to reference sibling files