[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASQG4YF543N644XECHM4PJ":3,"skill-same:01M7ASQG4YF543N644XECHM4PJ":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7ASQG4YF543N644XECHM4PJ","madrid-avisos",null,"Prepare, submit with user authorization, and check municipal reports at avisos.madrid.es. Use for Avisos Madrid, reporting street defects, cleaning, lighting or urban equipment in Madrid city, and requests for new street elements. Not for other municipalities, emergencies, or general administrative appeals.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: madrid-avisos\ndescription: Prepare, submit with user authorization, and check municipal reports at avisos.madrid.es. Use for Avisos Madrid, reporting street defects, cleaning, lighting or urban equipment in Madrid city, and requests for new street elements. Not for other municipalities, emergencies, or general administrative appeals.\n---\n\n# Madrid Avisos\n\nTurn the user's observations into an accurate municipal report. Speak Spanish\nunless the user requests another language. The portal is\n[Avisos Madrid](https:\u002F\u002Favisos.madrid.es\u002F).\n\n## Choose the available mode\n\n- With an interactive browser, inspect the live portal and carry the authorized\n  workflow through to its visible result. Use the host's supported browser tools.\n- With only search, HTTP extraction, or no browser, prepare a paste-ready draft\n  and a precise handoff. These capabilities cannot submit this JavaScript form.\n- A verified integration may replace browser steps only if its documented\n  capabilities cover the operation. Do not invent an API from frontend URLs.\n\nRead [portal.md](references\u002Fportal.md) when interacting with the website. Read\n[sessions.md](references\u002Fsessions.md) when reusing or establishing access, and\n[runtimes.md](references\u002Fruntimes.md) only for installation or capability issues.\nLoading this skill grants no additional permissions or browser access.\n\n## Gather and draft\n\n1. Extract the problem, exact incident location, and requested action from the\n   conversation. Reuse information already given. Ask a focused question only\n   for missing details that prevent an accurate report. A street number,\n   intersection, or identifiable landmark may resolve a vague location; do not\n   infer the incident location from the user's home, IP, or a photo's metadata.\n2. Distinguish **AVISO** (a problem with an existing street element) from\n   **PETICIÓN** (a requested new element). Check that the issue concerns Madrid\n   city. For immediate danger, direct the user to emergency services. For a\n   different municipality or a formal appeal, identify the appropriate channel\n   instead of treating this portal as a substitute.\n3. Write a concise Spanish description: observable problem, precise location,\n   reported duration or impact if supplied, and the requested intervention.\n   Do not invent dates, dimensions, causes, danger, ownership, or responsibility.\n   Preserve uncertainty and distinguish an observation from an allegation.\n4. Photos are optional. Use only attachments selected by the user for this report.\n   Do not generate evidence or upload unrelated files. Identify unnecessary\n   faces, identifying details, or private data before upload; offer omission or\n   a redacted copy and preserve originals. Never place contact details,\n   credentials, identity numbers, or banking details in the public description.\n\nDraft format, with unresolved fields clearly marked:\n\n```text\nTipo: AVISO \u002F PETICIÓN\nUbicación: [incident location, with any needed landmark]\nCategoría: [exact live option, or proposed category not yet verified]\nDescripción: [ready-to-paste Spanish text]\nAdjuntos: [selected files, or none]\nVisibilidad: [actual portal setting, or not yet verified]\nEstado: Borrador; no enviado\n```\n\n## Prepare the portal\n\n1. Keep the draft in the conversation before authentication or navigation that\n   could discard it. Check normal portal UI for a valid session and reuse the\n   host-managed browser profile. If authentication is needed, follow\n   [the session handoff](references\u002Fsessions.md): let the user sign in directly,\n   with no agent observation during credential entry. Account creation, OTP,\n   CAPTCHA, and legal acceptance also require user action under the host's rules.\n   Never request passwords or codes in chat, export cookies, copy credentials\n   between agents, create an account, or keep a session alive in the background.\n2. Make a focused check for an existing report at the same location and category.\n   Check relevant filters and detail before calling it a duplicate; an empty or\n   failed map is not proof that none exists. If the same incident is already\n   reported, show its reference and ask which action the user wants. Supporting,\n   commenting on, or reiterating it requires authorization for that action.\n3. Open **Nuevo reporte**, select the type, search the incident address, and\n   verify the normalized address and map marker. Do not use device geolocation\n   unless the user requests it. Select category labels from the current UI;\n   category availability and additional required fields can change.\n4. Fill the description and authorized attachments. Check attachment previews,\n   actual visibility, and category-specific fields. A visually enabled submit\n   button does not prove the form is complete. Read back the filled values.\n5. Present the concrete report for review: location, category, text, attachments,\n   visibility, and any contact data the selected category actually requires.\n   Explain that public report content can be read by other citizens. Do not\n   silently change visibility or promise confidentiality for a private report.\n\n## Submit and verify\n\n- Submission requires an explicit user instruction covering this report and\n  its destination. Creating a skill, preparing a draft, or opening the portal\n  is not permission to submit. Finish preparation before asking for any missing\n  approval; do not repeat approval already given unless the content, data,\n  destination, or a host-required confirmation changes.\n- Click the final submission control once. Wait for the result and inspect it.\n  Save the portal-issued ID, actual detail link if provided, current status,\n  and timestamp. A click, spinner, HTTP success code, login redirect, or filled\n  form is not evidence of registration.\n- If the request times out or its result is ambiguous, report **Envío no\n  confirmado**. Inspect **Mis reportes** or search the specific incident before\n  any retry. Do not submit again while the earlier outcome remains uncertain.\n- Respect the portal's daily limit and rate limits; do not work around them\n  with alternate accounts or repeated submissions.\n- Report **Registrado** only with portal confirmation. Quote the real reference\n  or state that the confirmation did not expose one. Otherwise say **Borrador**,\n  **Pendiente de acceso\u002Fautorización**, or **Envío no confirmado**, and identify\n  the next concrete step. Include confirmation evidence when the host supports\n  it, excluding account details.\n\nFor status requests, use the supplied ID or verified link and return the exact\ncurrent status with retrieval time. Do not equate **Fin de trámite** with a\nfixed incident without reading the resolution. Monitoring, notifications, and\nadditional external actions require their own user request.\n","# Madrid Avisos\n\nTurn the user's observations into an accurate municipal report. Speak Spanish\nunless the user requests another language. The portal is\n[Avisos Madrid](https:\u002F\u002Favisos.madrid.es\u002F).\n\n## Choose the available mode\n\n- With an interactive browser, inspect the live portal and carry the authorized\n  workflow through to its visible result. Use the host's supported browser tools.\n- With only search, HTTP extraction, or no browser, prepare a paste-ready draft\n  and a precise handoff. These capabilities cannot submit this JavaScript form.\n- A verified integration may replace browser steps only if its documented\n  capabilities cover the operation. Do not invent an API from frontend URLs.\n\nRead [portal.md](references\u002Fportal.md) when interacting with the website. Read\n[sessions.md](references\u002Fsessions.md) when reusing or establishing access, and\n[runtimes.md](references\u002Fruntimes.md) only for installation or capability issues.\nLoading this skill grants no additional permissions or browser access.\n\n## Gather and draft\n\n1. Extract the problem, exact incident location, and requested action from the\n   conversation. Reuse information already given. Ask a focused question only\n   for missing details that prevent an accurate report. A street number,\n   intersection, or identifiable landmark may resolve a vague location; do not\n   infer the incident location from the user's home, IP, or a photo's metadata.\n2. Distinguish **AVISO** (a problem with an existing street element) from\n   **PETICIÓN** (a requested new element). Check that the issue concerns Madrid\n   city. For immediate danger, direct the user to emergency services. For a\n   different municipality or a formal appeal, identify the appropriate channel\n   instead of treating this portal as a substitute.\n3. Write a concise Spanish description: observable problem, precise location,\n   reported duration or impact if supplied, and the requested intervention.\n   Do not invent dates, dimensions, causes, danger, ownership, or responsibility.\n   Preserve uncertainty and distinguish an observation from an allegation.\n4. Photos are optional. Use only attachments selected by the user for this report.\n   Do not generate evidence or upload unrelated files. Identify unnecessary\n   faces, identifying details, or private data before upload; offer omission or\n   a redacted copy and preserve originals. Never place contact details,\n   credentials, identity numbers, or banking details in the public description.\n\nDraft format, with unresolved fields clearly marked:\n\n```text\nTipo: AVISO \u002F PETICIÓN\nUbicación: [incident location, with any needed landmark]\nCategoría: [exact live option, or proposed category not yet verified]\nDescripción: [ready-to-paste Spanish text]\nAdjuntos: [selected files, or none]\nVisibilidad: [actual portal setting, or not yet verified]\nEstado: Borrador; no enviado\n```\n\n## Prepare the portal\n\n1. Keep the draft in the conversation before authentication or navigation that\n   could discard it. Check normal portal UI for a valid session and reuse the\n   host-managed browser profile. If authentication is needed, follow\n   [the session handoff](references\u002Fsessions.md): let the user sign in directly,\n   with no agent observation during credential entry. Account creation, OTP,\n   CAPTCHA, and legal acceptance also require user action under the host's rules.\n   Never request passwords or codes in chat, export cookies, copy credentials\n   between agents, create an account, or keep a session alive in the background.\n2. Make a focused check for an existing report at the same location and category.\n   Check relevant filters and detail before calling it a duplicate; an empty or\n   failed map is not proof that none exists. If the same incident is already\n   reported, show its reference and ask which action the user wants. Supporting,\n   commenting on, or reiterating it requires authorization for that action.\n3. Open **Nuevo reporte**, select the type, search the incident address, and\n   verify the normalized address and map marker. Do not use device geolocation\n   unless the user requests it. Select category labels from the current UI;\n   category availability and additional required fields can change.\n4. Fill the description and authorized attachments. Check attachment previews,\n   actual visibility, and category-specific fields. A visually enabled submit\n   button does not prove the form is complete. Read back the filled values.\n5. Present the concrete report for review: location, category, text, attachments,\n   visibility, and any contact data the selected category actually requires.\n   Explain that public report content can be read by other citizens. Do not\n   silently change visibility or promise confidentiality for a private report.\n\n## Submit and verify\n\n- Submission requires an explicit user instruction covering this report and\n  its destination. Creating a skill, preparing a draft, or opening the portal\n  is not permission to submit. Finish preparation before asking for any missing\n  approval; do not repeat approval already given unless the content, data,\n  destination, or a host-required confirmation changes.\n- Click the final submission control once. Wait for the result and inspect it.\n  Save the portal-issued ID, actual detail link if provided, current status,\n  and timestamp. A click, spinner, HTTP success code, login redirect, or filled\n  form is not evidence of registration.\n- If the request times out or its result is ambiguous, report **Envío no\n  confirmado**. Inspect **Mis reportes** or search the specific incident before\n  any retry. Do not submit again while the earlier outcome remains uncertain.\n- Respect the portal's daily limit and rate limits; do not work around them\n  with alternate accounts or repeated submissions.\n- Report **Registrado** only with portal confirmation. Quote the real reference\n  or state that the confirmation did not expose one. Otherwise say **Borrador**,\n  **Pendiente de acceso\u002Fautorización**, or **Envío no confirmado**, and identify\n  the next concrete step. Include confirmation evidence when the host supports\n  it, excluding account details.\n\nFor status requests, use the supplied ID or verified link and return the exact\ncurrent status with retrieval time. Do not equate **Fin de trámite** with a\nfixed incident without reading the resolution. Monitoring, notifications, and\nadditional external actions require their own user request.\n",{"name":5,"description":7},"main","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fmadrid-avisos",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add saski\u002Farnesto --skill madrid-avisos",{"tool":37,"command":38},"bunx","bunx skills add saski\u002Farnesto --skill madrid-avisos",{"tool":40,"command":41},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill madrid-avisos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002FSKILL.md",true,[45,51,55,59,63],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",216,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fevaluation.md",3242,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002Freferences\u002Fevaluation.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fportal.md",3307,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002Freferences\u002Fportal.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fruntimes.md",2994,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002Freferences\u002Fruntimes.md",{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fsessions.md",6149,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmadrid-avisos\u002Freferences\u002Fsessions.md",[68,75,82,89,96,103],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]