iflytek/iFly-Skills - Open Source PR Review Scorecard

Official collection of iFLYTEK skills for speech, OCR, translation, proofreading, and multimodal AI capabilities.

C-Rank Grade: S (Elite) - 71/100

External PR Merge Rate: 89%

Response Time: 3h

First Timer Success: 75%

Frequently Asked Questions

Is iflytek/iFly-Skills welcoming to first-time open-source contributors?

iflytek/iFly-Skills has a recorded first-timer success rate of 75.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in iflytek/iFly-Skills respond to incoming external pull requests in approximately 3.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 70.8 C-Rank™ score (S Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 70.8 places iflytek/iFly-Skills in the S tier.

What is the external contributor pull request merge rate for iflytek/iFly-Skills?

The external contributor pull request merge rate for iflytek/iFly-Skills is 88.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in iflytek/iFly-Skills?

iflytek/iFly-Skills currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

iflytek
iflytek/iFly-SkillsS•Elite209
GitHub
Back to Explorer
iflytek

iflytek/iFly-Skills

209
Active (30d)S•Elite(71/100)Python

Official collection of iFLYTEK skills for speech, OCR, translation, proofreading, and multimodal AI capabilities.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Active Open-Source Maintainer

Warmth Score
7.8/10
Patience Score
8.2/10
Nitpick Rate
20%

Active maintainer team in iflytek/iFly-Skills welcoming community pull requests and bug fixes.

Top PR Submission Do's

  • •Ensure code complies with repository style conventions
  • •Keep PRs focused and well-documented

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit unlinked PRs without context
  • •Do not break existing automated test suites
Response Velocity
3 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
88.6%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
75.0%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
4 core
Small core review team
Diagnostic Health HUD
88.6%
Merge Gauge
75.0%
1st-Timer
Community Vibe86/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for iflytek/iFly-Skills
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/iflytek/iFly-Skills)](https://getmerged.abhishekco.de/iflytek/iFly-Skills?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Summary Extend the distribution of iFly-Skills beyond the current Claude Code / local-script usage model by publishing to external registries and platforms. The goal is to meet users where they already work — whether that's an IDE, a bot platform, a workflow automation tool, or an IM client — so iFLYTEK AI capabilities become accessible to a much broader audience with zero friction. Motivation Publishing to registries and platforms that users already interact with daily, we can: Lower the barrier to entry — install via smithery install, npm install, or a one-click bot add Reach non-developer users — Coze bot builders, Dify workflow designers, IM group users Enable composition — skills become nodes in larger workflows (n8n), tools in AI pipelines (Dify), or plugins in bot ecosystems (Coze) Increase discoverability — users browsing Smithery, npm, or Coze marketplace discover iFly-Skills organically Platforms & Target Audience # Platform User Persona How Skills Are Consum

📅 Opened Jun 17, 2026💬 0 comments
Quality: 40/100Contribute

Expand the documentation FAQ 📖 The FAQ pages — docs/faq.md (English) and docs/zh/faq.md (中文) — are a high-traffic landing spot for new users. Help us grow them with real questions people hit. What to do Pick one or two common questions — good sources are recently closed issues, the Discussions, or anything that tripped you up during setup. Add a clear question + answer to docs/faq.md (English). Mirror the same entry in docs/zh/faq.md (中文) at the same position. Only comfortable in one language? Add that one and say so in your PR — someone can add the other. Preview locally: cd docs && npm run docs:dev Good candidates Credential / environment-variable pitfalls (XFEI_APP_ID / XFEI_API_KEY / XFEI_API_SECRET) "I get an authorization / service-not-enabled error" — which capability to activate in the console Which skill to use for a given task (OCR vs. invoice OCR, TTS vs. voice clone, …) How to call a specific skill from its SKILL.md How to register a skill inside

📅 Opened Jun 17, 2026💬 2 comments
Quality: 90/100Contribute

Contribute a skill or usage recipe 🧩 The Skill Catalog showcases reusable iFLYTEK skills that anyone can install and adapt. Adding a new skill — or a recipe that shows existing skills solving a real task — is a great first contribution, and you'll show up as a project contributor. Option A — add a new skill Package an iFLYTEK capability as a self-contained skill directory: ifly-<your-skill>/ ├── SKILL.md # frontmatter (name, description, metadata) + API docs & usage ├── scripts/ # runnable scripts; prefer the Python standard library └── _meta.json # metadata Copy an existing skill (e.g. ifly-translate) as a template. Write a clear SKILL.md — the frontmatter description and user_instructions decide when an agent triggers the skill; the body documents how to call it. Scrub secrets ⚠️ — read XFEI_APP_ID / XFEI_API_KEY / XFEI_API_SECRET from the environment and use YOUR_* placeholders in examples. Never commit real credentials. Add a

📅 Opened Jun 17, 2026💬 0 comments
Quality: 80/100Contribute

Help translate the iFly-Skills docs 🌏 Our documentation site uses a standard VitePress i18n layout: English is the default at the root, and each language mirrors it under its own folder (Simplified Chinese already lives under docs/zh/). Adding a language is one of the highest-impact, lowest-barrier ways to contribute — and you'll show up as a project contributor. We're looking for translators for: 🇯🇵 Japanese (ja) 🇰🇷 Korean (ko) 🇪🇸 Spanish (es) 🇫🇷 French (fr) …or propose another language you can maintain. How it works Each language is a folder under docs/ that mirrors the English pages with identical relative paths (e.g. docs/ja/guide/quick-start.md mirrors docs/guide/quick-start.md). The full workflow — running the site locally, where pages go, and how to register a new locale — is in the Contribute to the Docs guide. To get involved Comment below with the language you'd like to work on (and, if you want, which page you'll start with) so we don't

📅 Opened Jun 17, 2026💬 0 comments
Quality: 90/100Contribute

中文在下,English below. 你正在使用 iFly-Skills 吗?/ Are you using iFly-Skills? 首先,非常感谢你使用并支持 iFly-Skills!🎉 我们非常重视每一位用户的反馈,并会持续努力把这套基于科大讯飞 AI 能力(语音、OCR、翻译、校对、多模态理解等)的技能集合做得更好。 这个 issue 的目的 / Why this issue 我们希望在社区与用户之间建立连接,听到真实场景中的声音,并在你需要的时候提供帮助。如果你已经在评估或生产环境中使用了某个 iFly-Skill,欢迎在下方留言,让更多人看到你的应用案例。 我们希望你提供 / What we'd love to hear 请在评论区按以下格式留言(中英文皆可): 组织 / 公司名称 — Name of your organization or company 官网链接 — Link to your website 国家 / 地区 — Your country / region 联系方式(邮箱 / 微信 / X 等)— Your contact info 使用了哪些技能(如 Hyper TTS、Invoic

📅 Opened Jun 17, 2026💬 0 comments
Quality: 80/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for iflytek/iFly-Skills

When evaluating whether to contribute to iflytek/iFly-Skills, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of iflytek/iFly-Skills acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 88.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to iflytek/iFly-Skills

01

Is iflytek/iFly-Skills welcoming to first-time open-source contributors?

iflytek/iFly-Skills has a recorded first-timer success rate of 75.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~3 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 70.8 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 70.8 places iflytek/iFly-Skills in the Elite tier.

04

What is the external contributor pull request merge rate for iflytek/iFly-Skills?

The external pull request merge rate is 88.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in iflytek/iFly-Skills?

Yes, iflytek/iFly-Skills currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for iflytek/iFly-Skills are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.