技能详情（站内镜像，无评论）
作者：Angelos Panagiotakis @agelospanagiotakis
许可证：MIT-0
MIT-0 ·免费使用、修改和重新分发。无需归因。
版本：v0.0.1
统计：⭐ 0 · 283 · 0 current installs · 0 all-time installs
⭐ 0
安装量（当前） 0
🛡 VirusTotal ：可疑 · OpenClaw ：良性
Package：agelospanagiotakis/epragma-redmine-issue
安全扫描（ClawHub）
- VirusTotal ：可疑
- OpenClaw ：良性
OpenClaw 评估
The skill's code and instructions match its stated purpose (talking to a Redmine server using a URL and API key), but there are metadata/instruction mismatches and a buggy env-var handling implementation you should be aware of before using it in production.
目的
Name/description (read/create/update Redmine issues) align with the code and instructions. The skill legitimately needs a REDMINE_URL and REDMINE_API_KEY. However, registry metadata lists no required env vars while SKILL.md and the code require them; the code also accepts REDMINE_BASE_URL as an alternate which is undocumented in SKILL.md (memory note mentions swapped env support).
说明范围
SKILL.md tells the agent to run the included Node scripts which only call the Redmine REST API. The runtime instructions and code do not reference unrelated system files or external endpoints beyond the configured Redmine base URL.
安装机制
There is no install spec (instruction-only style). Code files are included but nothing is downloaded or auto-installed from external URLs, so install risk is low.
证书
Requested secrets (Redmine URL and API key) are proportionate to the skill. But the skill's metadata did not declare these required env vars, and the code also references REDMINE_BASE_URL and implements a swapped-vars fallback. This inconsistency could cause misconfiguration and surprises. Also the implementation of env-var handling appears buggy (see next guidance).
持久
The skill does not request persistent/system-wide privileges and always:false. It does not modify other skills or system settings.
综合结论
This skill appears to do what it says — interact with a Redmine instance using a base URL and API key — but check a few things before installing: - Verify and set the REDMINE_URL and REDMINE_API_KEY (the registry metadata omitted these even though SKILL.md and the code require them). The code also looks for REDMINE_BASE_URL as an alternate; decide which variables you'll use and be consistent. - Review and/or fix the env-var logic in scripts/li…
安装（复制给龙虾 AI）
将下方整段复制到龙虾中文库对话中，由龙虾按 SKILL.md 完成安装。
请把本段交给龙虾中文库（龙虾 AI）执行：为本机安装 OpenClaw 技能「Epragma Redmine Issue」。简介：Read Redmine issues from any Redmine server via REST API with configurable URL …。
请 fetch 以下地址读取 SKILL.md 并按文档完成安装：https://raw.githubusercontent.com/openclaw/skills/refs/heads/main/skills/agelospanagiotakis/epragma-redmine-issue/SKILL.md
（来源：yingzhi8.cn 技能库）SKILL.md
---
name: epragma-redmine-issue
description: Read Redmine issues from any Redmine server via REST API with configurable URL and credentials. Use when you need to fetch a single issue, list/filter issues, or inspect issue fields for change planning; supports deployment to different Redmine instances via environment variables.
user-invocable: true
---
# ePragma Redmine Issue
Read Redmine issues through REST API.
## Configuration
This skill requires `REDMINE_URL` and `REDMINE_API_KEY` to be configured.
### Setup with OpenClaw CLI
Run these commands to configure the skill:
```bash
# Set your Redmine URL
openclaw skills config epragma-redmine-issue set REDMINE_URL https://your-redmine-server.com
# Set your API key (generate from Redmine My Account page)
openclaw skills config epragma-redmine-issue set REDMINE_API_KEY your-api-key-here
```
### Get your API Key
1. Log in to your Redmine server
2. Go to "My Account"
3. Click "Show" next to "API access key"
4. Copy the key
## Get one issue
```bash
node {baseDir}/scripts/issues.mjs get --id 123
```
## List issues
```bash
node {baseDir}/scripts/issues.mjs list
node {baseDir}/scripts/issues.mjs list --project-id my-project --status-id open --limit 20 --offset 0
node {baseDir}/scripts/issues.mjs list --assigned-to-id me --sort "updated_on:desc"
node {baseDir}/scripts/issues.mjs list --project my-project
```
## List projects
```bash
node {baseDir}/scripts/issues.mjs projects
```
## List statuses
```bash
node {baseDir}/scripts/issues.mjs statuses
```
## Update one issue
```bash
node {baseDir}/scripts/issues.mjs update --id 123 --status-id 2 --notes "this is ok"
node {baseDir}/scripts/issues.mjs update --id 123 --assigned-to-id 6 --priority-id 3
node {baseDir}/scripts/issues.mjs update --id 123 --done-ratio 50 --notes "done 50%"
```
## Add comment to issue
```bash
node {baseDir}/scripts/issues.mjs comment --id 123 --notes "This is a comment"
```
## Create new issue
```bash
# Required: --project-id (or project name), --subject
# Optional: --description, --tracker-id, --priority-id, --assigned-to-id, --status-id, --start-date, --due-date, --done-ratio, --estimated-hours
node {baseDir}/scripts/issues.mjs create --project-id 1 --subject "New issue title"
node {baseDir}/scripts/issues.mjs create --project-id epragma --subject "Bug report" --description "Details here" --priority-id 4
```
## Time Entries
```bash
# List time entries (filters: --issue-id, --project-id, --user-id, --from, --to, --spent-on)
node {baseDir}/scripts/issues.mjs time-list
node {baseDir}/scripts/issues.mjs time-list --issue-id 232
node {baseDir}/scripts/issues.mjs time-list --project-id 1 --from 2026-01-01 --to 2026-01-31
# Add time entry (required: --issue-id OR --project-id, --hours; optional: --activity-id, --spent-on, --comments)
node {baseDir}/scripts/issues.mjs time-add --issue-id 232 --hours 2 --activity-id 9 --comments "Work done"
node {baseDir}/scripts/issues.mjs time-add --project-id 1 --hours 1.5 --activity-id 8
# List available activities
node {baseDir}/scripts/issues.mjs time-activities
```
## Notes
- URL and auth are variables by design for cross-environment deployment.
- API responses are output as JSON.
- For automation, prefer `REDMINE_API_KEY` over username/password.