From Fresh Clone to Merged PR: The Contributing Skill

Where this fits

You're an agent tasked with helping a developer contribute to an open-source project. The developer asks "what can I work on?" or "is my change ready to submit?" — and you need to navigate a repo you've never seen, respect project conventions, and avoid wasting the maintainer's time. The contributing skill encodes the full path from a fresh clone to a merged pull request for Tel-Agent, an AGPL-3.0 AI phone assistant. It turns a vague request into a guided, rule-abiding contribution workflow.

Why agents benefit

• Starts with the right context: The skill forces reading CLAUDE.md first, so the agent understands the project's working contract before making any decisions.
• Encodes non-negotiable rules: It explicitly checks for English-only content and bans naming competitors — irreversible mistakes that would waste everyone's time.
• Covers the whole lifecycle: From picking an issue, setting up the repo, starting/finishing tasks, to opening a PR, the skill provides step-by-step guidance at every stage.
• Answers common contributor questions: It handles "how do I start?" and "is my change ready?" with concrete checks, not generic advice.
• Reduces maintainer burden: By enforcing quality gates upfront, the skill helps agents produce submissions that are more likely to be accepted.

Practical scenarios

Onboarding a new contributor

A developer wants to make their first contribution to Tel-Agent. The agent uses the skill to walk them through repository setup, explains the contribution workflow, and helps them pick a suitable first issue — all while adhering to the project's language and naming rules.

Mid-task check before pushing

An agent has been implementing a feature for Tel-Agent. Before opening a pull request, it consults the skill to verify that the change meets all requirements: English-only code, no competitor references, and proper commit messages. This catches issues early.

Asking "what can I work on?"

A developer asks the agent for task suggestions. The skill provides a structured approach to scan open issues, filter by labels or difficulty, and propose actionable tasks that align with the project's priorities and the developer's skill level.

Add it to your agent workflow

Install the skill with:

npx skills add Dpro-at/Tel-Agent --skill contributing

Once installed, the agent can invoke it automatically when it detects a contribution request. Example usage:

User: "I want to help with Tel-Agent. Where do I start?"
Agent: (triggers contributing skill) "Let me first read CLAUDE.md to understand the project contract..."

The skill then guides the agent through the repository structure, setup commands, and contribution checklist.

Compare before adopting

Before adding this skill to your agent's toolkit, compare it with alternatives:

• Quality signals: Check the repository's activity, number of stars (currently 46), and whether the skill is maintained by the project maintainers (here, Dpro-at).
• Maintenance freshness: Look for recent commits and updates to the skill definition.
• Alternatives: Generic contribution guides might exist, but they won't know Tel-Agent's specific rules.
• Workflow fit: Ensure the skill's instructions align with how your agent typically handles GitHub interactions.

Why it is worth tracking

This skill is a strong example of a project-specific contribution assistant. Its quality signals include a clear, authoritative README, explicit rule enforcement, and direct integration with the project's own documentation. The community momentum is modest but steady, and the skill is maintained by the project author, which increases trust. Evaluate it when you need to onboard agents into Tel-Agent or similar open-source projects. For a full overview, see the skill page on OpenAgentSkill. Tracking it now gives you a template for building similar contribution skills for other repositories.