> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/guides/sharing-your-skills.md). # Sharing Your Skills Your skills inventory helps Built By DAO understand what its members can do together. Record the abilities you already bring, describe your experience accurately and name the skills you want to develop. Those details help connect individual interests with community needs. ## Think Beyond Your Usual Role Include useful experience from employment, volunteering, study, personal projects and everyday responsibilities. A member known for organizing events may also know bookkeeping, woodworking or a language a project needs. The purpose is to make that capacity easier to recognize and connect with work. The shared catalog organizes skills into lanes and categories. Search the Skills Directory by skill, category or keyword, then add the relevant skills to your own inventory. Using the same catalog helps members and projects describe related abilities in a consistent way. ## Describe What You Can Do Today Choose the proficiency that best reflects your current ability. Think about the kind of work you can complete and the support you would need. | Proficiency | Practical Meaning | | ------------ | ----------------------------------------------------------------- | | Novice | You are building the fundamentals and need supervision. | | Basic | You can complete simple tasks with guidance. | | Intermediate | You can work independently within the skill. | | Advanced | You can handle complex work and help others develop. | | Expert | You bring deep mastery and can guide difficult or strategic work. | Add the experience and certification details relevant to the skill where available. Accurate information helps a project have a useful conversation about fit. A self-recorded proficiency or certification entry is a description to discuss alongside the qualifications the work requires. ## Keep Learning Goals Distinct Use a learning goal for something you want to learn. That interest helps describe where you want to grow; it is different from a skill you already have. The inventory keeps those meanings separate so a team's existing capacity is not confused with its future ambitions. A novice skill is still a current skill. Choose it when you are practicing the fundamentals and can describe the support you need. Use the learning goal when the ability is something you want to begin developing. ## Connect the Inventory with Real Work Find Tasks uses your recorded skills to help surface relevant opportunities. You can also explore tasks you could learn on. Open the task, understand the required outcome and consider its effort and deadline before deciding to claim it. Skills are one part of a workable commitment. Bring your interest and actual availability into the conversation with the project lead, especially when the work depends on other people or a fixed schedule. See [Choosing Your Work](/guides/choosing-your-work.md) for the claim, work and review journey. ## Help the Community Understand Its Capacity Taken together, member records support a broader picture of the network. Skills coverage describes the abilities recorded across the organization or a working group. Gap analysis compares recorded skills with requirements, and task matching helps identify relevant member experience for a particular task. This can inform practical questions: do we have the experience a project needs, where would training help, and what support should we find before taking on more work? Learning interests add another dimension by showing where members want to develop. The Skills Directory is a searchable catalog of skills to add to your inventory. Access to member details and project-specific matching follows the app's visibility rules. Use the information available in your role and project context when discussing who can help. ## Keep Your Record Useful over Time Update the inventory when your experience grows, your learning interests change or an entry no longer describes you well. Your skills manager lets you edit proficiency and details or remove an outdated entry. Use completed work and reviewer feedback to reflect on what you can do reliably. A useful inventory develops with the person behind it. As the community's records improve, so does its basis for recognizing hidden capacity and finding complementary contributors. ## A Network Built from Complementary Contributions In an **illustrative workshop project**, a repair specialist, an organizer and a documentation contributor bring different strengths. A member interested in learning maintenance can discuss an appropriate supported role. The shared inventory gives the project a starting point for understanding that mix, while the actual work and conversations establish the commitments. The ambition is for the whole network to understand more of what it already has, develop the abilities it needs and give each member a clearer way to participate. {% content-ref url="/pages/xo8oDsBWJ5sWtkvPFr6B" %} [All Guides](/guides/guides.md) {% endcontent-ref %} {% content-ref url="/pages/a70fUSkUcY0wo1Q2OM2L" %} [Choosing Your Work](/guides/choosing-your-work.md) {% endcontent-ref %} {% content-ref url="/pages/w0zDTT61RFryBvqRSyzK" %} [Guilds & Working Groups](/membership/guilds.md) {% endcontent-ref %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.builtbydao.com/guides/sharing-your-skills.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.