Skill install instructions in #259 won't be discovered by Claude Code

Abierto
#290 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
58/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
markdown, python

Línea de trabajo

Read the skill file at skills/nameres.md and the install instructions introduced in PR #259. Check Claude Code's expected skill directory and frontmatter format, then move the skill to skills/nameres/SKILL.md, add a name and trigger-focused description, and update installation to copy the directory into .claude/skills/. Done when the documented install path exposes /nameres and the Markdown body remains usable in other agents.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Noticed while building the equivalent skill for NodeNorm (NodeNormalization#403 follow-on), and worth fixing so the two services install the same way.

PR #259 ships the skill as skills/nameres.md and tells users to save it as:

mkdir -p .claude/skills
curl -o .claude/skills/nameres.md ...

then says "Claude Code will make it available as /nameres".

Claude Code discovers skills as <skills-dir>/<skill-name>/SKILL.md, with YAML frontmatter supplying name and description — for example:

~/.claude/skills/nameres/SKILL.md
---
name: nameres
description: Resolve biomedical names to CURIEs ...
---

A bare .claude/skills/nameres.md is not picked up at all, so /nameres will not exist and the skill will never load automatically. (#259 is marked WIP, so this may already be on the list.)

Suggested fix, which is what NodeNorm is doing:

  • Move the file to skills/nameres/SKILL.md.
  • Add frontmatter with name and a description written to help the model decide when to load it — mentioning concrete triggers, e.g. resolving a name or label to a CURIE.
  • Change the install instructions to copy the skills/nameres/ directory into .claude/skills/.
  • The body stays plain Markdown, so pasting it into any other agent still works.

The description matters more than it looks: it is what the model matches against to decide whether the skill is relevant, so it should name the situations that should trigger it rather than just describing the service.

Lenguaje dominante
Python
Estrellas
5
Forks
4
Métricas de merge de PR
Sin PR fusionados en 30 d

Preparar el entorno

  • Incluye un Dockerfile o un archivo de Docker Compose
  • Sin plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NCATSTranslator/NameResolution

Todos los issues de NCATSTranslator/NameResolution

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.