ワンクリックでManusで任意のスキルを実行

satisfaction-feedback

Handle user satisfaction feedback. When users respond with "satisfied"/"unsatisfied", update FAQ usage count or record BADCASE. Trigger words: satisfied/unsatisfied/resolved/not resolved/thanks/满意/不满意/解决了/没解决/谢谢.

Manusで実行

概要

インストールコマンド

npx skills add https://github.com/Harryoung/efka --skill satisfaction-feedback

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

Harryoung/efka

スター101

フォーク19

更新日2026年1月17日 14:22

ファイルエクスプローラー

2 ファイル

SKILL.md

readonly

name	satisfaction-feedback
description	Handle user satisfaction feedback. When users respond with "satisfied"/"unsatisfied", update FAQ usage count or record BADCASE. Trigger words: satisfied/unsatisfied/resolved/not resolved/thanks/满意/不满意/解决了/没解决/谢谢.

Satisfaction Feedback Processing

Process user satisfaction feedback and update FAQ or record issues based on the answer source.

Trigger Words

Satisfied: satisfied, resolved, thanks, understood, ok, got it, clear, I see, 满意, 解决了, 谢谢, 明白了, 好的, 懂了, 清楚了, 知道了 Unsatisfied: unsatisfied, not resolved, wrong, incorrect, doesn't work, 不满意, 没解决, 不对, 错了, 不行

Processing Logic

Process feedback based on answer source from previous round (metadata answer_source):

Answer Source	Satisfied Feedback	Unsatisfied Feedback
FAQ	Increment usage count	Remove entry + Record BADCASE
Knowledge base file	Add to FAQ	Record BADCASE

Key Principles

Use file locks: Must use SharedKBAccess file locks when updating FAQ.md and BADCASE.md
Concurrency safety: Avoid data conflicts when multiple users operate simultaneously
Status update: Set session_status to "resolved" after satisfied feedback

Detailed Operations

For FAQ add/delete/modify operation details, see FAQ_OPERATIONS.md

このリポジトリの他の Skills

同じリポジトリ

batch-notification

Harryoung/efka

Send IM messages to users in batch. Used for notifying specific user groups, sending after table filtering, all-staff notifications, etc. Use this Skill when administrators request batch notifications, mass messaging, or notifications after table filtering. Trigger words: notify/send/mass + users/batch/table.

2026-01-17101

document-conversion

Harryoung/efka

Convert DOC/DOCX/PDF/PPT/PPTX documents to Markdown format. Automatically detect PDF type (electronic/scanned), extract images to separate directory. Use this Skill when administrator onboards non-Markdown documents. Trigger condition: Onboard DOC/DOCX/PDF/PPT/PPTX format files.

2026-01-17101

expert-routing

Harryoung/efka

Domain expert routing. When the knowledge base cannot answer user questions, find and notify the corresponding expert based on the question domain. Only available in IM mode. Trigger condition: No results in 6-stage retrieval.

2026-01-17101

large-file-toc

Harryoung/efka

Generate table of contents overview for large files. When onboarded Markdown file exceeds threshold (default 30KB), extract heading structure to create navigation file. Trigger condition: Markdown file size >= 30KB.

2026-01-17101

excel-parser

Harryoung/efka

Smart Excel/CSV file parsing with intelligent routing based on file complexity analysis. Analyzes file structure (merged cells, row count, table layout) using lightweight metadata scanning, then recommends optimal processing strategy - either high-speed Pandas mode for standard tables or semantic HTML mode for complex reports. Use when processing Excel/CSV files with unknown or varying structure where optimization between speed and accuracy is needed.

2026-01-06101

ソース

Harryoung

Harryoung/efka

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

カスタマーサービス担当者オフィス・行政サポート職43-4051L4

name	satisfaction-feedback
description	Handle user satisfaction feedback. When users respond with "satisfied"/"unsatisfied", update FAQ usage count or record BADCASE. Trigger words: satisfied/unsatisfied/resolved/not resolved/thanks/满意/不满意/解决了/没解决/谢谢.

Satisfaction Feedback Processing

Process user satisfaction feedback and update FAQ or record issues based on the answer source.

Trigger Words

Processing Logic

Process feedback based on answer source from previous round (metadata answer_source):

Answer Source	Satisfied Feedback	Unsatisfied Feedback
FAQ	Increment usage count	Remove entry + Record BADCASE
Knowledge base file	Add to FAQ	Record BADCASE

Key Principles

Use file locks: Must use SharedKBAccess file locks when updating FAQ.md and BADCASE.md
Concurrency safety: Avoid data conflicts when multiple users operate simultaneously
Status update: Set session_status to "resolved" after satisfied feedback

Detailed Operations

For FAQ add/delete/modify operation details, see FAQ_OPERATIONS.md