> For the complete documentation index, see [llms.txt](https://wiki.oikos-international.org/oikosmos/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.oikos-international.org/oikosmos/starter-kit/community-engagement/chapter-check-ins.md).

# Chapter Check-ins

It is key to stay in close touch with our community — and to support each chapter individually, listening and responding to their local needs. Thus, we invite chapters twice a year for **1-on-1 check-ins** with one of our board members. The 1 hour calls listen into the future projects, perspectives and needs of our community and help us to sharpen our international initiatives.

Chapter check-ins occur biannualy. Feel free to reach out to oikos International to schedule a call, or oikos board member will reach out to you!

<details>

<summary>Some things that we usually touch upon in the check-in calls:</summary>

* Successes and Highlights
* Challenges and Lowlights
* Goals and Future Ambitions
* Needs and Questions (how can oikos International or oikos community support you?)

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.oikos-international.org/oikosmos/starter-kit/community-engagement/chapter-check-ins.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.