Distilly — Distill how they think into reusable Skills for any Agent or Bot. Formerly Colleague Skill（原同事 Skill）.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 7%
Response Time: -
First Timer Success: -
titanwings/distilly has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in titanwings/distilly respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 49.0 places titanwings/distilly in the B tier.
The external contributor pull request merge rate for titanwings/distilly is 6.7%, based on public PR activity from non-core contributors.
titanwings/distilly currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in titanwings/distilly. Reviews community pull requests with focus on project quality.
Discussions in titanwings/distilly focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/titanwings/distilly?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (8% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Problem The --setup flow of every auto-collector reads API tokens and passwords via input(), which echoes characters to the terminal and leaves them in shell scrollback / session recordings. Example from tools/confluence_auto_collector.py: api_token = input("API Token: ").strip() # visible password = input("Password: ").strip() # visible Same pattern exists in the Feishu, Slack, and DingTalk collectors. Proposed fix Use getpass.getpass() for any prompt that reads a secret (token, password, app secret). Display name / email / URL can stay as input(). from getpass import getpass api_token = getpass("API Token: ").strip() password = getpass("Password: ").strip() Affected files tools/feishu_auto_collector.py tools/slack_auto_collector.py tools/dingtalk_auto_collector.py tools/confluence_auto_collector.py (pending PR #106) Why good-first-issue Two-line change per file. Minimal Python knowledge required. A great way to submit your first PR while learning the codebase. Acceptance c
Problem All *_auto_collector.py tools write credential configs (API tokens, passwords) to ~/.colleague-skill/*_config.json using Path.write_text(...), which respects the user's umask — on most systems that ends up as 0644 (world-readable within the user account's processes). This means any process running as the same user can read tokens in plaintext. Affected files tools/feishu_auto_collector.py — save_config() around line 72 tools/slack_auto_collector.py — save_config() around line 102 tools/dingtalk_auto_collector.py tools/confluence_auto_collector.py (pending PR #106) — save_config() around line 89 Proposed fix In each collector's save_config(), after writing the file: import os CONFIG_PATH.write_text(json.dumps(config, indent=2, ensure_ascii=False)) os.chmod(CONFIG_PATH, 0o600) Also ensure the parent directory is created with restrictive perms: CONFIG_PATH.parent.mkdir(parents=True, exist_ok=True, mode=0o700) Why good-first-issue Small, mechanical change across 3-4 files
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to titanwings/distilly, 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 titanwings/distilly acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 6.7% were successfully merged into the primary branch.
titanwings/distilly has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 49.0 places titanwings/distilly in the Solid tier.
The external pull request merge rate is 6.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, titanwings/distilly currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for titanwings/distilly 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.