Is Feedback · Yoodaddy0311 safe and trustworthy?

tashan scores Feedback · Yoodaddy0311 on public evidence — tashan score 44.0/100, it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Feedback · Yoodaddy0311?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Feedback · Yoodaddy0311?

2 GitHub contributors, source: Yoodaddy0311/artibot.

‹ The Index

Feedback · Yoodaddy0311

skill

Author’s activation text, quoted as published

| Auto-captures user bug reports and feature requests, conducts a structured interview, and creates a GitHub issue on the Artibot repository — all without the user typing any slash-command. Triggered by natural complaint/request language. MUST trigger when user says any of: - "버그", "버그 신고", "이상해", "안 돼", "안 됨", "작동 안 해", "에러 나", "오류 나" - "기능 요청", "이런 기능 있으면", "추가해주면", "~되게 해줘" - "개선해줘", "불편해", "느려", "느린 것 같아" - "bug", "broken", "doesn't work", "feature request", "please add" DO NOT trigger for: - Casual frustration about unrelated things ("오늘 날씨 이상해") - Questions about how something works ("이거 어떻게 써?") - Rhetorical complaints inside code ("이 코드 이상하네" during review) The user never needs to. …

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r feedback ~/.claude/skills/

tashan score: 44.0
Adoption: 2 repos
Upkeep: 78.0
Freshness: 92.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 2
License: NOASSERTION

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it and shows worked examples.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Feedback · Yoodaddy0311 scores 44 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/skill-yoodaddy0311-feedback.svg)](https://tashan.sh/capability/skill-yoodaddy0311-feedback.html)

source ↗ · skill:Yoodaddy0311/feedback

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-16 · scorer s5 · how · something wrong here?