skills.rest
tawf-labs
tawf-labsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Feedback

Submit issue or praise feedback for ethskills content with a message and target skill.

1|Updated Jan 24, 2026
Search Tags:#feedback#documentation#developer experience#safety#issues#praise
One-click install
npx skills add https://github.com/tawf-labs/zkt-hackathon --skill feedback-tawf-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Feedback
Source: https://github.com/tawf-labs/zkt-hackathon/tree/main/.agents/skills/ethskills/feedback
Command: npx skills add https://github.com/tawf-labs/zkt-hackathon --skill feedback-tawf-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you provide actionable feedback about ethskills content, so incorrect, confusing, missing, or especially helpful guidance can be improved for future users.

Core Features & Use Cases

  • Issue feedback: Report when a skill is wrong, stale, misleading, missing key warnings, or confusing enough to cause friction.
  • Praise feedback: Share what worked well, including specific examples of skills that saved time or prevented mistakes.
  • Clean, safe submissions: Emphasizes stripping sensitive data (no PII like addresses, private keys, emails, or real names) before sending.

Quick Start

Tell the ethskills team whether a specific skill was misleading, wrong, or genuinely helpful, and describe what happened without including any sensitive personal data.

Frequently Asked Questions about Feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report an issue or error in developer documentation?▼

To report an issue in developer documentation, you can submit feedback specifying the kind as an issue, providing a message and the target skill. This helps identify misleading, stale, or confusing guidance for correction.

Can I send praise for documentation that provided a good developer experience?▼

Yes, you can send praise for documentation that provided a good developer experience by submitting feedback with the kind specified as praise. Share specific examples of guidance that saved time or prevented mistakes.

What information do I need to include when submitting feedback on a specific skill?▼

When submitting feedback on a specific skill, you need to provide a feedback payload specifying the kind as issue or praise, a detailed message, and the target skill. Scrubbing any sensitive data before submitting is recommended.

Do I need to remove sensitive data before sending feedback on safety issues?▼

Yes, you must remove sensitive data before sending feedback on safety issues or any other topic. Strip all PII including addresses, private keys, emails, and real names from your message before submitting to the endpoint.

What types of documentation problems are best suited for issue feedback?▼

Issue feedback is best suited for documentation problems like wrong, stale, misleading, or missing key warnings. It also applies to guidance that is confusing enough to cause friction when building with the platform.

Related Skills

Explore More Content & Communication Skills→
iani-kuliiani-kuli

secret-guard

Block hardcoded credentials and API keys during git commit workflows.

Community
Advanced
fmflurryfmflurry
171

skills-skill-learned-user-corrections

Extract user corrections into reusable rules and validate outputs against updated expectations.

Community
Intermediate
jonathimerjonathimer
84

competitor-tracking

Track competitor features, pricing, and sentiment to generate battlecards.

Community
Intermediate
Oz-NetworksOz-Networks
6

mirra-feedback

Report bugs, feedback, and feature requests through a REST API.

Official
Intermediate