feat(installer): Add selective install filters and new skill

Add installer filters for risk, category, and tags so maintainers and
users can ship smaller skill surfaces to context-sensitive runtimes.
Document the reduced-install flow for OpenCode-style hosts, add the
humanize-chinese community skill, and sync the generated catalog and
plugin-safe artifacts that now reflect the release batch.

Refs #437
Refs #440
Refs #443
This commit is contained in:
sickn33
2026-04-03 17:08:33 +02:00
parent db36188c78
commit bb2304a34f
36 changed files with 4076 additions and 158 deletions

View File

@@ -1,7 +1,7 @@
{
"name": "antigravity-awesome-skills",
"version": "9.4.0",
"description": "Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,327 supported skills.",
"description": "Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,330 supported skills.",
"author": {
"name": "sickn33 and contributors",
"url": "https://github.com/sickn33/antigravity-awesome-skills"

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,146 @@
---
name: humanize-chinese
description: Detect and rewrite AI-like Chinese text with a practical workflow for scoring, humanization, academic AIGC reduction, and style conversion. Use when the user asks to 去AI味, 降AIGC, 去除AI痕迹, 论文降重, 知网检测, 维普检测, humanize chinese, detect AI text, or make Chinese text sound more natural.
category: content
risk: safe
source: community
tags:
- chinese
- writing
- editing
- aigc
- academic
- style-transfer
date_added: "2026-04-03"
---
# Humanize Chinese
Use this skill when you need to detect AI-like Chinese writing, rewrite it to feel less synthetic, reduce AIGC signals in academic prose, or convert the text into a more specific Chinese writing style.
## When to Use
- Use when the user says `去AI味`, `降AIGC`, `去除AI痕迹`, `让文字更自然`, `改成人话`, or `降低AI率`
- Use when the user wants a Chinese text checked for AI-writing patterns or suspicious phrasing
- Use when the user wants academic-paper-specific AIGC reduction for CNKI, VIP, or Wanfang-style checks
- Use when the user wants Chinese text rewritten into a different style such as `zhihu`, `xiaohongshu`, `wechat`, `weibo`, `literary`, or `academic`
## Core Workflow
### 1. Detect Before Rewriting
Start by identifying the most obvious AI markers instead of rewriting blindly:
- rigid `first/second/finally` structures
- mechanical connectors such as `综上所述`, `值得注意的是`, `由此可见`
- abstract grandiose wording with low information density
- repeated sentence rhythm and paragraph length
- academic prose that sounds too complete, too certain, or too template-driven
If the user provides a short sample, call out the suspicious phrases directly before rewriting.
### 2. Rewrite in the Smallest Useful Pass
Prefer targeted rewrites over total regeneration:
- remove formulaic connectors rather than paraphrasing every sentence
- vary sentence length and paragraph rhythm
- replace repeated verbs and noun phrases
- swap abstract summaries for concrete observations where possible
- keep the original claims, facts, citations, and terminology intact
### 3. Validate the Result
After rewriting, verify that the text:
- still says the same thing
- sounds less templated
- uses more natural rhythm
- does not introduce factual drift
- stays in the correct register for the target audience
For academic text, preserve a scholarly tone. Do not over-casualize.
## Optional CLI Flow
If the user has a local clone of the source toolkit, these examples are useful:
```bash
python3 scripts/detect_cn.py text.txt -v
python3 scripts/compare_cn.py text.txt -a -o clean.txt
python3 scripts/academic_cn.py paper.txt -o clean.txt --compare
python3 scripts/style_cn.py text.txt --style xiaohongshu -o out.txt
```
Use this CLI sequence when available:
1. detect and inspect suspicious sentences
2. rewrite or compare
3. rerun detection on the cleaned file
4. optionally convert into a target style
## Manual Rewrite Playbook
If the scripts are unavailable, use this manual process.
### Common AI Markers
- numbered or mirrored structures that feel too symmetrical
- filler transitions that add no meaning
- repeated stock phrases
- overly even sentence length
- conclusions that sound final, polished, and risk-free
### Rewrite Moves
- delete weak transitions first
- collapse repetitive phrases into one stronger sentence
- split sentences at natural turns instead of forcing long balanced structures
- merge choppy sentences when they feel robotic
- replace generic abstractions with concrete wording
- introduce light variation in cadence so the prose does not march at a constant tempo
## Academic AIGC Reduction
For papers, reports, or theses:
- keep discipline-specific terminology unchanged
- replace AI-academic stock phrases with more grounded scholarly phrasing
- reduce absolute certainty with measured hedging where appropriate
- vary paragraph structure so each section does not read like the same template
- add limitations or uncertainty if the conclusion feels unnaturally complete
Examples of safer direction changes:
- `本文旨在` -> `本文尝试` or `本研究关注`
- `具有重要意义` -> `值得关注` or `有一定参考价值`
- `研究表明` -> `前人研究发现` or `已有文献显示`
Do not invent citations, evidence, or data.
## Style Conversion
Use style conversion only after the base text is readable and natural.
Supported style directions from the source workflow:
- `casual`
- `zhihu`
- `xiaohongshu`
- `wechat`
- `academic`
- `literary`
- `weibo`
When switching style, keep the user's meaning stable and change only tone, structure, and surface wording.
## Output Rules
- Show the main AI-like patterns you found
- Explain the rewrite strategy in 1-3 short bullets
- Return the rewritten Chinese text
- If helpful, include a short note on remaining weak spots
## Source
Adapted from the `voidborne-d/humanize-chinese` project and its CLI/script workflow for Chinese AI-text detection and rewriting.

View File

@@ -0,0 +1,48 @@
---
name: uxui-principles
description: "Evaluate interfaces against 168 research-backed UX/UI principles, detect antipatterns, and inject UX context into AI coding sessions."
category: design
risk: safe
source: community
date_added: "2026-04-03"
author: uxuiprinciples
tags: [ux, ui, design, evaluation, principles, antipatterns, accessibility]
tools: [claude, cursor, windsurf]
---
# UX/UI Principles
A collection of 5 agent skills for evaluating interfaces against 168 research-backed UX/UI principles, detecting antipatterns, and injecting UX context into AI-assisted design and coding sessions.
**Source:** https://github.com/uxuiprinciples/agent-skills
## Skills
| Skill | Purpose |
|-------|---------|
| `uxui-evaluator` | Evaluate interface descriptions against 168 research-backed principles |
| `interface-auditor` | Detect UX antipatterns using the uxuiprinciples smell taxonomy |
| `ai-interface-reviewer` | Audit AI-powered interfaces against 44 AI-era UX principles |
| `flow-checker` | Check user flows against decision, error, and feedback principles |
| `vibe-coding-advisor` | Inject UX context into vibe coding sessions before implementation |
## When to Use
- Auditing an existing interface for UX issues
- Checking if a UI follows research-backed best practices
- Detecting antipatterns and UX smells in designs
- Reviewing AI-powered interfaces for trust, transparency, and safety
- Getting UX guidance before or during implementation
## How It Works
1. Install any skill from the collection
2. Describe the interface, screen, or flow you want to evaluate
3. The skill evaluates against the relevant principles and returns structured findings with severity levels and remediation steps
4. Optionally connect to the uxuiprinciples.com API for enriched output with full citations
## Install
```
npx skills add uxuiprinciples/agent-skills
```

View File

@@ -19,7 +19,7 @@
"skills": "./skills/",
"interface": {
"displayName": "Antigravity Awesome Skills",
"shortDescription": "1,311 plugin-safe skills for coding, security, product, and ops workflows.",
"shortDescription": "1,314 plugin-safe skills for coding, security, product, and ops workflows.",
"longDescription": "Install a plugin-safe Codex distribution of Antigravity Awesome Skills. Skills that still need hardening or target-specific setup remain available in the repo but are excluded from this plugin.",
"developerName": "sickn33 and contributors",
"category": "Productivity",

File diff suppressed because it is too large Load Diff

View File

@@ -0,0 +1,146 @@
---
name: humanize-chinese
description: Detect and rewrite AI-like Chinese text with a practical workflow for scoring, humanization, academic AIGC reduction, and style conversion. Use when the user asks to 去AI味, 降AIGC, 去除AI痕迹, 论文降重, 知网检测, 维普检测, humanize chinese, detect AI text, or make Chinese text sound more natural.
category: content
risk: safe
source: community
tags:
- chinese
- writing
- editing
- aigc
- academic
- style-transfer
date_added: "2026-04-03"
---
# Humanize Chinese
Use this skill when you need to detect AI-like Chinese writing, rewrite it to feel less synthetic, reduce AIGC signals in academic prose, or convert the text into a more specific Chinese writing style.
## When to Use
- Use when the user says `去AI味`, `降AIGC`, `去除AI痕迹`, `让文字更自然`, `改成人话`, or `降低AI率`
- Use when the user wants a Chinese text checked for AI-writing patterns or suspicious phrasing
- Use when the user wants academic-paper-specific AIGC reduction for CNKI, VIP, or Wanfang-style checks
- Use when the user wants Chinese text rewritten into a different style such as `zhihu`, `xiaohongshu`, `wechat`, `weibo`, `literary`, or `academic`
## Core Workflow
### 1. Detect Before Rewriting
Start by identifying the most obvious AI markers instead of rewriting blindly:
- rigid `first/second/finally` structures
- mechanical connectors such as `综上所述`, `值得注意的是`, `由此可见`
- abstract grandiose wording with low information density
- repeated sentence rhythm and paragraph length
- academic prose that sounds too complete, too certain, or too template-driven
If the user provides a short sample, call out the suspicious phrases directly before rewriting.
### 2. Rewrite in the Smallest Useful Pass
Prefer targeted rewrites over total regeneration:
- remove formulaic connectors rather than paraphrasing every sentence
- vary sentence length and paragraph rhythm
- replace repeated verbs and noun phrases
- swap abstract summaries for concrete observations where possible
- keep the original claims, facts, citations, and terminology intact
### 3. Validate the Result
After rewriting, verify that the text:
- still says the same thing
- sounds less templated
- uses more natural rhythm
- does not introduce factual drift
- stays in the correct register for the target audience
For academic text, preserve a scholarly tone. Do not over-casualize.
## Optional CLI Flow
If the user has a local clone of the source toolkit, these examples are useful:
```bash
python3 scripts/detect_cn.py text.txt -v
python3 scripts/compare_cn.py text.txt -a -o clean.txt
python3 scripts/academic_cn.py paper.txt -o clean.txt --compare
python3 scripts/style_cn.py text.txt --style xiaohongshu -o out.txt
```
Use this CLI sequence when available:
1. detect and inspect suspicious sentences
2. rewrite or compare
3. rerun detection on the cleaned file
4. optionally convert into a target style
## Manual Rewrite Playbook
If the scripts are unavailable, use this manual process.
### Common AI Markers
- numbered or mirrored structures that feel too symmetrical
- filler transitions that add no meaning
- repeated stock phrases
- overly even sentence length
- conclusions that sound final, polished, and risk-free
### Rewrite Moves
- delete weak transitions first
- collapse repetitive phrases into one stronger sentence
- split sentences at natural turns instead of forcing long balanced structures
- merge choppy sentences when they feel robotic
- replace generic abstractions with concrete wording
- introduce light variation in cadence so the prose does not march at a constant tempo
## Academic AIGC Reduction
For papers, reports, or theses:
- keep discipline-specific terminology unchanged
- replace AI-academic stock phrases with more grounded scholarly phrasing
- reduce absolute certainty with measured hedging where appropriate
- vary paragraph structure so each section does not read like the same template
- add limitations or uncertainty if the conclusion feels unnaturally complete
Examples of safer direction changes:
- `本文旨在` -> `本文尝试` or `本研究关注`
- `具有重要意义` -> `值得关注` or `有一定参考价值`
- `研究表明` -> `前人研究发现` or `已有文献显示`
Do not invent citations, evidence, or data.
## Style Conversion
Use style conversion only after the base text is readable and natural.
Supported style directions from the source workflow:
- `casual`
- `zhihu`
- `xiaohongshu`
- `wechat`
- `academic`
- `literary`
- `weibo`
When switching style, keep the user's meaning stable and change only tone, structure, and surface wording.
## Output Rules
- Show the main AI-like patterns you found
- Explain the rewrite strategy in 1-3 short bullets
- Return the rewritten Chinese text
- If helpful, include a short note on remaining weak spots
## Source
Adapted from the `voidborne-d/humanize-chinese` project and its CLI/script workflow for Chinese AI-text detection and rewriting.

View File

@@ -0,0 +1,48 @@
---
name: uxui-principles
description: "Evaluate interfaces against 168 research-backed UX/UI principles, detect antipatterns, and inject UX context into AI coding sessions."
category: design
risk: safe
source: community
date_added: "2026-04-03"
author: uxuiprinciples
tags: [ux, ui, design, evaluation, principles, antipatterns, accessibility]
tools: [claude, cursor, windsurf]
---
# UX/UI Principles
A collection of 5 agent skills for evaluating interfaces against 168 research-backed UX/UI principles, detecting antipatterns, and injecting UX context into AI-assisted design and coding sessions.
**Source:** https://github.com/uxuiprinciples/agent-skills
## Skills
| Skill | Purpose |
|-------|---------|
| `uxui-evaluator` | Evaluate interface descriptions against 168 research-backed principles |
| `interface-auditor` | Detect UX antipatterns using the uxuiprinciples smell taxonomy |
| `ai-interface-reviewer` | Audit AI-powered interfaces against 44 AI-era UX principles |
| `flow-checker` | Check user flows against decision, error, and feedback principles |
| `vibe-coding-advisor` | Inject UX context into vibe coding sessions before implementation |
## When to Use
- Auditing an existing interface for UX issues
- Checking if a UI follows research-backed best practices
- Detecting antipatterns and UX smells in designs
- Reviewing AI-powered interfaces for trust, transparency, and safety
- Getting UX guidance before or during implementation
## How It Works
1. Install any skill from the collection
2. Describe the interface, screen, or flow you want to evaluate
3. The skill evaluates against the relevant principles and returns structured findings with severity levels and remediation steps
4. Optionally connect to the uxuiprinciples.com API for enriched output with full citations
## Install
```
npx skills add uxuiprinciples/agent-skills
```