TeX good first issues

This feature request aims to enable one-line installation of AI research skills from this repository using the `gh skill` command, a GitHub CLI extension for Claude Code skill management. Currently, users must manually clone or copy skill files, and this change would significantly lower friction and improve discoverability for Claude Code users.

This bug report identifies a broken link within the project's documentation. The incorrect URL `https://allcontributors.org/en/emoji-key` should be corrected to `https://allcontributors.org/en/reference/emoji-key/`. The reporter suspects this error might be present in multiple locations within the documentation.

The current EuropeCV LaTeX template is outdated and needs to be updated to match the style of a provided Word document. The issue proposes developing a new style file (.sty) to achieve this, suggesting it could be a project for AI tools. The author is seeking community input and investigation due to personal time constraints.

The user is reporting a bug where page breaks are occurring incorrectly in their document, specifically after a horizontal rule that precedes a new section. This is happening unexpectedly between the rule and the subsequent section text.

This issue requests the recovery and addition of missing music and installation proceedings to a collection. The task involves identifying merged proceedings and searching for potentially unpublished documents or program information on archived conference websites or from chairs.

This issue describes a data quality problem where words are joined together in abstract text due to line breaks in PDF extraction. This issue is most prevalent in abstracts from 2003-2013 and also appears in 2026, breaking full-text search functionality. The suggested fix involves comparing extracted text against the original PDF to identify and correct these joined words.

The style guide for using figures needs an update to include an example of embedding figures from other parts of the book. This would demonstrate a more advanced feature for reusing visual content within the documentation.

This issue proposes merging the 'Music' and 'Installations' proceedings tracks for publications, starting from 2024. The goal is to unify these tracks for previous years as well, ensuring consistency in how published works are categorized, particularly for differentiating between Live Performance, Remote Performance, and Installation types.

This issue requests the addition of music and installation information for the NIME 2010 conference. The contributor has provided links to a PDF program, a DOCX file with concert programs, and a website with installation details. The task involves extracting and organizing this information into the bibliography.

This issue describes a problem where a recent change to automatically strip trailing whitespace in R files is causing significant disruption. It leads to numerous unrelated file modifications and merge conflicts in pull requests. The proposed solution is a one-time cleanup PR to remove all existing trailing whitespace from the `devel` branch, preventing future issues.

This issue proposes improving the indexing of NIME proceedings in DBLP by including references. The suggestion is to explore integrating with the OpenCitations.net database to achieve this.

This issue requires setting up ACM indexing for NIME publications. The core task is to convert older publications into the new XML format used by ACM, as indexing stopped after 2014. This involves understanding ACM's current XML schema and developing a conversion process.

This issue proposes creating BibTeX files for both former music and installation tracks. The core question is whether installation tracks should be included in the same BibTeX files as music tracks or managed separately.

This issue proposes an enhancement to improve Google Scholar's indexing of nime.org. The user suggests exploring the use of BibTeX browser tools to format the site's content in a way that Google Scholar can better process and index.

This issue proposes organizing BibTeX entries related to music and installations into separate files. Currently, these entries are mixed within the main paper BibTeX file and should be relocated for better structure.

This issue requests the addition of music and installation information from the NIME 2016 event. The necessary resources, including images, concert videos, and shared files, are provided via Flickr, Vimeo, and Google Drive links.

This issue requests the addition of NIME 2008 music and installation information to the repository. The necessary program notes have been found and are provided as two PDF attachments, which are noted as being properly formatted for separate uploads.

This issue reports a broken link within the Turing Way documentation. The link, intended to point to a Jupyter Book page, now leads to a nonexistent URL. This is a straightforward bug fix requiring the correction of a single hyperlink.

This issue describes work towards a specific research goal (MAIS-O16) by implementing a proof checker and a cooperating "FairBot_k". The current progress involves a working proof checker, and the next steps are to implement the FairBot and determine a cooperation threshold. The complexity arises from the potential for large proof sizes with the current system.

This issue proposes improving the documentation for rarefaction by moving a detailed explanation earlier in the text and providing practical examples of using the `rarefyAssay()` function with the `niter` parameter for alpha and beta diversity calculations. It also aims to clarify the differences between related functions like `addAlpha()` vs `getAlpha()` and `runMDS()` vs `addMDS()`.

This is a community discussion thread for users to request new language translations for a project. Users are instructed to first search for their desired language and upvote existing requests, or create a new comment with their language if it's not already listed.

This GitHub issue outlines a comprehensive to-do list for the "2026 release" of a document, likely an orientation guide for new students. It includes tasks ranging from content updates and proofreading to technical Git operations and checking external information like opening hours and course details.

This issue proposes a discussion to design new Human-Robot Interaction (HRI) tasks for RoboCup that are more challenging and impactful for research. The goal is to move beyond simple dialogues and incorporate multi-modal interactions, social cues, and adaptive strategies, addressing current limitations in robot attentiveness and interaction fluidity.

This issue seeks to establish community norms regarding development workflows, specifically whether contributors should use forks or branches within the main repository. The goal is to discuss and decide on a preferred approach, then update documentation and educate new members accordingly.

This issue highlights a lack of user understanding regarding proper colcon workspace setup, specifically concerning the `colcon_defaults.yaml` file and colon mixins. The goal is to improve documentation or provide clearer guidance to address this common confusion.

The `run_demo.py` script duplicates significant functionality already present in `FewShotPrompter`. This leads to maintenance issues as changes need to be applied in two places. The proposed fix is to refactor `run_demo.py` to be a simple CLI wrapper that utilizes the existing `FewShotPrompter` class, eliminating the redundant code.

This issue proposes adding support for linking personal profiles on external academic platforms like ORCID, Google Scholar, and DBLP to user profiles on the DICE teams page. This would allow researchers to connect their profiles and make them more discoverable for others within and outside the team. The proposed solutions involve using RDF properties or `owl:sameAs` for data representation and icons for web page rendering.