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

未关闭
#290 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
58/100
Issue 类型
文档
描述清晰度
描述清楚
活跃度
停滞
技术栈
markdown, python

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
5
派生
4
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NCATSTranslator/NameResolution 的其他 Issue

查看 NCATSTranslator/NameResolution 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。